2132
CanFollow 782 Exposed IOCTL with Insufficient Access Control 1648
CanPrecede 822 Untrusted Pointer Dereference 1723
Applicable Platforms
Language : C (Prevalence = Often)
Language : C++ (Prevalence = Often)
Operating_System : Windows NT (Prevalence = Sometimes)
Common Consequences
Scope Impact Likelihood
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.
Potential Mitigations
Phase: 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
CWE Version 4.14
CWE-781: Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code
CWE-781: Improper Address Validation in
IOCTL with METHOD_NEITHER I/O Control Code