CWE一覧に戻る
CWE-781

METHOD_NEITHER I/O 制御コードを持つ IOCTL での不適切なアドレス検証

Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code
脆弱性 レビュー中
JA

この製品は、I/OにMETHOD_NEITHERを使用するIOCTLを定義しているが、提供されたアドレスを検証しないか、誤って検証している。

IOCTLがI/O制御にMETHOD_NEITHERオプションを使用する場合、IOCTLに供給されたアドレスを検証するのはIOCTLの責任である。バリデーションが欠落しているか不正確な場合、攻撃者は任意のメモリーアドレスを供給することができ、コードの実行やサービス拒否につながる。

EN

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.

Scope: Integrity, Availability, Confidentiality / Impact: Modify Memory; Read Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart
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.
MITRE公式ページ — CWE-781