CWE · MITRE source
CWE-782Exposed 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.
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.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 2 mapping(s) from 2 framework(s): ASVS 5.0 1 (mostly) · ATT&CK 1 (mostly)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2021-21551 KEV | 10.0 | 8.8 | 0.5747 | 2021-05-04 |
CVE-2024-30804 | 7.0 | 9.8 | 0.0082 | 2024-04-26 |
CVE-2024-32370 | 7.0 | 9.8 | 0.0104 | 2024-05-07 |
CVE-2024-4196 | 7.0 | 10.0 | 0.0059 | 2024-06-25 |
CVE-2024-39251 | 7.0 | 10.0 | 0.0072 | 2024-07-01 |
CVE-2021-21786 | 5.5 | 7.8 | 0.0029 | 2021-07-07 |
CVE-2021-21787 | 5.5 | 8.8 | 0.0034 | 2021-07-07 |
CVE-2021-21788 | 5.5 | 8.8 | 0.0032 | 2021-07-07 |
CVE-2021-21789 | 5.5 | 8.8 | 0.0032 | 2021-07-07 |
CVE-2021-25695 | 5.5 | 7.8 | 0.0028 | 2021-07-21 |
CVE-2023-35841 | 5.5 | 7.8 | 0.0037 | 2024-05-14 |
CVE-2024-33218 | 5.5 | 7.8 | 0.0021 | 2024-05-22 |
CVE-2024-33219 | 5.5 | 7.8 | 0.0026 | 2024-05-22 |
CVE-2024-33220 | 5.5 | 8.8 | 0.0070 | 2024-05-22 |
CVE-2024-33221 | 5.5 | 7.8 | 0.0018 | 2024-05-22 |
CVE-2024-33222 | 5.5 | 8.4 | 0.0019 | 2024-05-22 |
CVE-2025-26125 | 5.5 | 7.3 | 0.0048 | 2025-03-17 |
CVE-2025-8061 | 5.5 | 7.0 | 0.0037 | 2025-09-11 |
CVE-2025-47761 | 5.5 | 7.8 | 0.0014 | 2025-11-18 |
CVE-2026-36355 UPD | 5.5 | 7.7 | 0.0068 | 2026-05-05 |
CVE-2026-8501 UPD | 5.5 | 7.8 | 0.0016 | 2026-06-01 |
CVE-2021-21785 | 3.5 | 5.5 | 0.0034 | 2021-08-05 |
CVE-2021-21790 | 3.5 | 5.5 | 0.0034 | 2021-08-05 |
CVE-2021-21791 | 3.5 | 5.5 | 0.0034 | 2021-08-05 |
CVE-2021-21792 | 3.5 | 5.5 | 0.0034 | 2021-08-05 |