Skip to content
OpenAdvisories

Weakness (CWE)

CWE-782: Exposed IOCTL with Insufficient Access Control

Variant Draft

The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.

More detail

When 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.

How to prevent it (1 mitigation)

  1. Architecture and Design

    In Windows environments, use proper access control for the associated device or device namespace. See References.

Source: MITRE CWE-782

All Critical High Medium Low Exploited only Public exploit

3 results · Clear filters · Feed

  • Low 2.0
    CVE-2026-16003

    Exposed IOCTL with Insufficient Access Control in Armoury Crate driver allows a local user to add an arbitrary process …

    ASUS Armoury Crate
  • Low 2.0
    CVE-2026-6737

    An Exposed IOCTL with Insufficient Access Control vulnerability in AsusPTPFilter allows a local user to bypass driver s…

    ASUS AsusPTPFilter
  • Low 3.2
    CVE-2023-44976 Public exploit

    Hangzhou Shunwang Rentdrv2 before 2024-12-24 allows local users to terminate EDR processes and possibly have unspecifie…

    Hangzhou Shunwang Rentdrv2