CWE-782
Exposed IOCTL with Insufficient Access Control
2009-07-27
00h00 +00:00
00h00 +00:00
指定 CWE 通知
掌握特定 CWE 的任何變更。
名稱: Exposed IOCTL with Insufficient Access Control
The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.
一般資訊
引入方式
Architecture and DesignImplementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.
適用平台
程式語言
名稱： C (Often)名稱： C++ (Often)
作業系統
類別： Unix (Undetermined)類別： Windows (Undetermined)
常見後果
| 範圍 | 影響 | 可能性 |
|---|---|---|
| Integrity Availability Confidentiality | Varies by Context 注意：Attackers can invoke any functionality that the IOCTL offers. Depending on the functionality, the consequences may include code execution, denial-of-service, and theft of data. |
觀察到的案例
| 參考資料 | 描述 |
|---|---|
CVE-2009-2208 | Operating system does not enforce permissions on an IOCTL that can be used to modify network settings. |
CVE-2008-3831 | Device driver does not restrict ioctl calls to its direct rendering manager. |
CVE-2008-3525 | ioctl does not check for a required capability before processing certain requests. |
CVE-2008-0322 | Chain: insecure device permissions allows access to an IOCTL, allowing arbitrary memory to be overwritten. |
CVE-2007-4277 | Chain: anti-virus product uses weak permissions for a device, leading to resultant buffer overflow in an exposed IOCTL. |
CVE-2007-1400 | Chain: sandbox allows opening of a TTY device, enabling shell commands through an exposed ioctl. |
CVE-2006-4926 | Anti-virus product uses insecure security descriptor for a device driver, allowing access to a privileged IOCTL. |
CVE-1999-0728 | Unauthorized user can disable keyboard or mouse by directly invoking a privileged IOCTL. |
潛在緩解措施
Phases : Architecture and DesignIn Windows environments, use proper access control for the associated device or device namespace. See References.
漏洞對應備注
理由說明 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.備註 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
備注
This 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.參考資料
REF-701
Securing Device ObjectsMicrosoft.
https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/controlling-device-access
提交
| 名稱 | 機構 | 日期 | 發布日期 | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 1.5 |
修改記錄
| 名稱 | 機構 | 日期 | 備註 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Time_of_Introduction | |
| CWE Content Team | MITRE | updated Likelihood_of_Exploit, Modes_of_Introduction, Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated References, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Weakness_Ordinalities |
