CWE-781
Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code
2009-07-27
00h00 +00:00
00h00 +00:00
특정 CWE 알림
특정 CWE의 변경 사항에 대한 정보를 받아보세요.
이름: Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code
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.
일반 정보
취약점 도입 방식
Implementation적용 가능한 플랫폼
언어
이름: C (Often)이름: C++ (Often)
운영 체제
이름: Windows NT (Sometimes)일반적인 결과
| 범위 | 영향 | 가능성 |
|---|---|---|
| Integrity Availability Confidentiality | Modify Memory, Read Memory, Execute Unauthorized Code or Commands, DoS: Crash, Exit, or Restart 참고: If validation is missing or incorrect, an attacker can supply arbitrary memory addresses for 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. |
관찰된 예시
| 참고 자료 | 설명 |
|---|---|
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. |
잠재적 완화 방법
Phases : ImplementationIf 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.
Phases : 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.
Phases : 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.
취약점 매핑 메모
근거 : 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.
메모
참고 자료
REF-696
Exploiting Common Flaws in DriversRuben Santamarta.
http://reversemode.com/index.php?option=com_content&task=view&id=38&Itemid=1
REF-697
Remote and Local Exploitation of Network DriversYuriy Bulygin.
https://www.blackhat.com/presentations/bh-usa-07/Bulygin/Presentation/bh-usa-07-bulygin.pdf
REF-698
Windows driver vulnerabilities: the METHOD_NEITHER odysseyAnibal Sacco.
http://www.net-security.org/dl/insecure/INSECURE-Mag-18.pdf
REF-699
Buffer Descriptions for I/O Control CodesMicrosoft.
https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/buffer-descriptions-for-i-o-control-codes
REF-700
Using Neither Buffered Nor Direct I/OMicrosoft.
https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/using-neither-buffered-nor-direct-i-o
REF-701
Securing Device ObjectsMicrosoft.
https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/controlling-device-access
REF-702
Exploiting Windows Device DriversPiotr Bania.
https://www.piotrbania.com/all/articles/ewdd.pdf
제출
| 이름 | 조직 | 날짜 | 출시일 | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 1.5 |
수정 사항
| 이름 | 조직 | 날짜 | 댓글 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Common_Consequences, Potential_Mitigations, References, Time_of_Introduction | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Likelihood_of_Exploit, References | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated References, Relationships, Time_of_Introduction | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Common_Consequences, Description |
