Exposed IOCTL with Insufficient Access Control
Description The software implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL. Extended DescriptionWhen an IOCTL contains privileged functionality and is exposed unnecessarily, attackers may be able to access this functionality by invoking the IOCTL. Even if the functionality is benign, if the programmer has assumed that the IOCTL would only be accessed by a trusted process, there may be little or no validation of the incoming data, exposing weaknesses that would never be reachable if the attacker cannot call the IOCTL directly.The implementations of IOCTLs will differ between operating system types and versions, so the methods of attack and prevention may vary widely. Likelihood of Exploit: Low to Medium Applicable PlatformsLanguage: OftenLanguage: CLanguage: OftenLanguage: C++Operating System Class: UNIX-basedOperating System Class: Windows-based Time Of Introduction
Common Consequences
Detection MethodsNone Potential Mitigations
RelationshipsThis can be primary to many other weaknesses when the programmer assumes that the IOCTL can only be accessed by trusted parties. For example, a program or driver might not validate incoming addresses in METHOD_NEITHER IOCTLs in Windows environments (CWE-781), which could allow buffer overflow and similar attacks to take place, even when the attacker never should have been able to access the IOCTL at all.
Demonstrative ExamplesNone Observed Examples
White Box Definitions None Black Box Definitions None Taxynomy MappingsNone References:
|