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: 09 May 2026 03:25 UTC
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. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-31201 KEV | 4.1 | 9.8 | 0.0225 | 2025-04-16 |
CVE-2026-33825 KEV | 3.9 | 7.8 | 0.0485 | 2026-04-14 |
CVE-2024-42365 | 3.4 | 7.4 | 0.3195 | 2024-08-08 |
CVE-2022-2475 | 2.0 | 9.8 | 0.0025 | 2022-10-28 |
CVE-2026-6356 | 1.9 | 9.6 | 0.0003 | 2026-04-22 |
CVE-2022-36110 | 1.8 | 8.8 | 0.0030 | 2022-09-09 |
CVE-2023-40070 | 1.8 | 8.8 | 0.0016 | 2024-05-16 |
CVE-2023-45217 | 1.8 | 8.8 | 0.0016 | 2024-05-16 |
CVE-2025-29987 | 1.8 | 8.8 | 0.0041 | 2025-04-03 |
CVE-2025-4404 | 1.8 | 9.1 | 0.0029 | 2025-06-17 |
CVE-2025-7493 | 1.8 | 9.1 | 0.0011 | 2025-09-30 |
CVE-2025-8049 | 1.8 | 8.8 | 0.0005 | 2025-10-20 |
CVE-2025-8053 | 1.8 | 9.1 | 0.0004 | 2025-10-20 |
CVE-2026-6388 | 1.8 | 9.1 | 0.0003 | 2026-04-15 |
CVE-2023-33127 | 1.7 | 8.1 | 0.0164 | 2023-07-11 |
CVE-2023-44285 | 1.6 | 7.8 | 0.0006 | 2023-12-14 |
CVE-2023-43040 | 1.6 | 6.5 | 0.0575 | 2024-05-14 |
CVE-2024-5389 | 1.6 | 8.1 | 0.0013 | 2024-06-09 |
CVE-2024-52799 | 1.6 | 8.2 | 0.0005 | 2024-11-21 |
CVE-2024-53295 | 1.6 | 7.8 | 0.0009 | 2025-02-01 |
CVE-2021-31384 | 1.5 | 7.2 | 0.0037 | 2021-10-19 |
CVE-2023-27591 | 1.5 | 7.5 | 0.0049 | 2023-03-17 |
CVE-2024-8927 | 1.5 | 7.5 | 0.0045 | 2024-10-08 |
CVE-2024-13256 | 1.5 | 7.5 | 0.0030 | 2025-01-09 |
CVE-2023-31342 | 1.5 | 7.5 | 0.0003 | 2025-02-11 |