CWE-782: Exposed IOCTL with Insufficient Access Control

Extended Description

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.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-782 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-782, Exposed IOCTL with Insufficient Access Control, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Exposed IOCTL with Insufficient Access Control during Architecture and Design

MITRE associates mitigation with Architecture and Design; recorded impacts include Varies by Context; observed examples include CVE-2009-2208, CVE-2008-3831, and CVE-2008-3525. Use these source-defined anchors to turn CWE-782 into implementation, review, and verification checks for the affected component.

CWE-782: Exposed IOCTL with Insufficient Access Control — MITRE CWE

Triage CWE-782 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-782, Exposed IOCTL with Insufficient Access Control, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-782

Apply MITRE's full root-cause mapping guidance when using CWE-782, Exposed IOCTL with Insufficient Access Control. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-782 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-782, Exposed IOCTL with Insufficient Access Control. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-782: Exposed IOCTL with Insufficient Access Control?+

CWE-782: Exposed IOCTL with Insufficient Access Control is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL. 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.

What are the security consequences of Exposed IOCTL with Insufficient Access Control?+

If exploited, CWE-782 (Exposed IOCTL with Insufficient Access Control) it can compromise Integrity, Availability and Confidentiality, leading to outcomes such as Varies by Context.

How do you prevent or mitigate Exposed IOCTL with Insufficient Access Control?+

Recommended mitigations for CWE-782 include: In Windows environments, use proper access control for the associated device or device namespace. See References.

Which programming languages are affected by Exposed IOCTL with Insufficient Access Control?+

CWE-782 commonly affects C and C++. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Exposed IOCTL with Insufficient Access Control?+

MITRE documents real CVEs mapped to CWE-782, including CVE-2009-2208, CVE-2008-3831, CVE-2008-3525, CVE-2008-0322 and CVE-2007-4277. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-782 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-782: Exposed IOCTL with Insufficient Access Control

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

Observed CVE Examples (8)

CWE Relationships

Parent Weaknesses