CWE · MITRE source
CWE-1220Insufficient Granularity of Access Control
The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.
Integrated circuits and hardware engines can expose accesses to assets (device configuration, keys, etc.) to trusted firmware or a software module (commonly set by BIOS/bootloader). This access is typically access-controlled. Upon a power reset, the hardware or system usually starts with default values in registers, and the trusted firmware (Boot firmware) configures the necessary access-control protection. A common weakness that can exist in such protection schemes is that access controls or policies are not granular enough. This condition allows agents beyond trusted agents to access assets and could lead to a loss of functionality or the ability to set up the device securely. This further results in security risks from leaked, sensitive, key material to modification of device configuration.
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 · 15 mapping(s) from 6 framework(s): ASVS 5.0 5 (mostly) · ATT&CK 4 (partial) · CSF 2.0 2 (mostly) · CAPEC 2 (partial) · STIG windows server 2016 1 (partial) · STIG windows server 2022 1 (partial)
NIST 800-53 r5 controls that address this weakness (5)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-2 | Separation of System and User Functionality | SC | Provides the necessary granularity by placing system management functions outside the reach of user-level access controls. |
SC-3 | Security Function Isolation | SC | Isolation supplies an explicit, enforceable granularity boundary between security and non-security functions that coarser access-control schemes lack. |
AC-16 | Security and Privacy Attributes | AC | Use of granular security and privacy attributes enables finer access control than coarse permission models alone. |
CA-9 | Internal System Connections | CA | Documenting interface characteristics enables more granular control over internal access. |
SA-17 | Developer Security and Privacy Architecture and Design | SA | Requires the architecture to describe granularity and placement of controls, preventing insufficiently fine-grained access decisions. |
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-2025-31201 KEV UPD | 10.0 | 9.8 | 0.1236 | 2025-04-16 |
CVE-2026-33825 KEV | 10.0 | 7.8 | 0.0675 | 2026-04-14 |
CVE-2022-2475 | 7.0 | 9.8 | 0.0060 | 2022-10-28 |
CVE-2025-4404 UPD | 7.0 | 9.1 | 0.0183 | 2025-06-17 |
CVE-2025-7493 | 7.0 | 9.1 | 0.0052 | 2025-09-30 |
CVE-2025-8053 | 7.0 | 9.1 | 0.0024 | 2025-10-20 |
CVE-2026-6388 UPD | 7.0 | 9.1 | 0.0036 | 2026-04-15 |
CVE-2026-6356 | 7.0 | 9.6 | 0.0029 | 2026-04-22 |
CVE-2026-2651 UPD | 7.0 | 9.0 | 0.0034 | 2026-05-25 |
CVE-2021-31384 | 5.5 | 7.2 | 0.0112 | 2021-10-19 |
CVE-2022-36110 | 5.5 | 8.8 | 0.0070 | 2022-09-09 |
CVE-2023-27591 | 5.5 | 7.5 | 0.0076 | 2023-03-17 |
CVE-2023-33127 | 5.5 | 8.1 | 0.0198 | 2023-07-11 |
CVE-2023-44285 | 5.5 | 7.8 | 0.0022 | 2023-12-14 |
CVE-2023-40070 | 5.5 | 8.8 | 0.0020 | 2024-05-16 |
CVE-2023-45217 | 5.5 | 8.8 | 0.0020 | 2024-05-16 |
CVE-2024-5389 | 5.5 | 8.1 | 0.0043 | 2024-06-09 |
CVE-2024-39323 | 5.5 | 7.1 | 0.0044 | 2024-07-02 |
CVE-2024-42365 | 5.5 | 7.4 | 0.0470 | 2024-08-08 |
CVE-2024-8927 | 5.5 | 7.5 | 0.0108 | 2024-10-08 |
CVE-2024-52799 | 5.5 | 8.2 | 0.0021 | 2024-11-21 |
CVE-2024-13256 | 5.5 | 7.5 | 0.0039 | 2025-01-09 |
CVE-2024-53295 | 5.5 | 7.8 | 0.0014 | 2025-02-01 |
CVE-2023-31342 | 5.5 | 7.5 | 0.0018 | 2025-02-11 |
CVE-2023-31343 | 5.5 | 7.5 | 0.0018 | 2025-02-11 |