Description
The product 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.
Potential Impact
Integrity, Availability, Confidentiality
Modify Memory, Read Memory, Execute Unauthorized Code or Commands, DoS: Crash, Exit, or Restart
Mitigations & Prevention
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.
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.
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.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2006-2373 | Driver for file-sharing and messaging protocol allows attackers to execute arbitrary code. |
| CVE-2009-0686 | Anti-virus product does not validate addresses, allowing attackers to gain SYSTEM privileges. |
| CVE-2009-0824 | DVD software allows attackers to cause a crash. |
| CVE-2008-5724 | Personal firewall allows attackers to gain SYSTEM privileges. |
| CVE-2007-5756 | chain: device driver for packet-capturing software allows access to an unintended IOCTL with resultant array index error. |
Related Weaknesses
Frequently Asked Questions
What is CWE-781?
CWE-781 (Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Variant-level weakness. The product defines an IOCTL that uses METHOD_NEITHER for I/O, but it does not validate or incorrectly validates the addresses that are provided.
How can CWE-781 be exploited?
Attackers can exploit CWE-781 (Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code) to modify memory, read memory, execute unauthorized code or commands, dos: crash, exit, or restart. This weakness is typically introduced during the Implementation phase of software development.
How do I prevent CWE-781?
Key mitigations include: 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
What is the severity of CWE-781?
CWE-781 is classified as a Variant-level weakness (Low-Medium abstraction). It has been observed in 5 real-world CVEs.