CWE-781 在METHOD_NEITHERIO控制代码中的IOCTL地址验证不恰当

Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code

结构: Simple

Abstraction: Variant

状态: Draft

被利用可能性: unkown

基本描述

The software defines an IOCTL that uses METHOD_NEITHER for I/O, but it does not validate or incorrectly validates the addresses that are provided.

扩展描述

When an IOCTL uses the METHOD_NEITHER option for I/O control, it is the responsibility of the IOCTL to validate the addresses that have been supplied to it. If validation is missing or incorrect, attackers can supply arbitrary memory addresses, leading to code execution or a denial of service.

相关缺陷

• cwe_Nature: ChildOf cwe_CWE_ID: 20 cwe_View_ID: 1000 cwe_Ordinal: Primary

• cwe_Nature: ChildOf cwe_CWE_ID: 20 cwe_View_ID: 699 cwe_Ordinal: Primary

• cwe_Nature: CanPrecede cwe_CWE_ID: 822 cwe_View_ID: 699

适用平台

Language: [{'cwe_Name': 'C', 'cwe_Prevalence': 'Often'}, {'cwe_Name': 'C++', 'cwe_Prevalence': 'Often'}]

Operating_System: {'cwe_Name': 'Windows NT', 'cwe_Prevalence': 'Sometimes'}

常见的影响

范围	影响	注释
['Integrity', 'Availability', 'Confidentiality']	['Modify Memory', 'Read Memory', 'Execute Unauthorized Code or Commands', 'DoS: Crash, Exit, or Restart']	An attacker may be able to access memory that belongs to another process or user. If the attacker can control the contents that the IOCTL writes, it may lead to code execution at high privilege levels. At the least, a crash can occur.

可能的缓解方案

Implementation

策略:

If METHOD_NEITHER is required for the IOCTL, then ensure that all user-space addresses are properly validated before they are first accessed. The ProbeForRead and ProbeForWrite routines are available for this task. Also properly protect and manage the user-supplied buffers, since the I/O Manager does not do this when METHOD_NEITHER is being used. See References.

Architecture and Design

策略:

If possible, avoid using METHOD_NEITHER in the IOCTL and select methods that effectively control the buffer size, such as METHOD_BUFFERED, METHOD_IN_DIRECT, or METHOD_OUT_DIRECT.

['Architecture and Design', 'Implementation']

策略:

If the IOCTL is part of a driver that is only intended to be accessed by trusted users, then use proper access control for the associated device or device namespace. See References.

分析过的案例

标识	说明	链接
CVE-2006-2373	Driver for file-sharing and messaging protocol allows attackers to execute arbitrary code.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2373
CVE-2009-0686	Anti-virus product does not validate addresses, allowing attackers to gain SYSTEM privileges.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0686
CVE-2009-0824	DVD software allows attackers to cause a crash.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0824
CVE-2008-5724	Personal firewall allows attackers to gain SYSTEM privileges.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5724
CVE-2007-5756	chain: device driver for packet-capturing software allows access to an unintended IOCTL with resultant array index error.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5756

Notes

Applicable Platform

Research Gap

引用

• REF-696 Exploiting Common Flaws in Drivers

• REF-697 Remote and Local Exploitation of Network Drivers

• REF-698 Windows driver vulnerabilities: the METHOD_NEITHER odyssey

• REF-699 Buffer Descriptions for I/O Control Codes

• REF-700 Using Neither Buffered Nor Direct I/O

• REF-701 Securing Device Objects

• REF-702 Exploiting Windows Device Drivers

文章来源于互联网:scap中文网