CWE · MITRE source
CWE-1191On-Chip Debug and Test Interface With Improper Access Control
The chip does not implement or does not correctly perform access control to check whether users are authorized to access internal registers and test modes through the physical debug/test interface.
A device's internal information may be accessed through a scan chain of interconnected internal registers, usually through a JTAG interface. The JTAG interface provides access to these registers in a serial fashion in the form of a scan chain for the purposes of debugging programs running on a device. Since almost all information contained within a device may be accessed over this interface, device manufacturers typically insert some form of authentication and authorization to prevent unintended use of this sensitive information. This mechanism is implemented in addition to on-chip protections that are already present. If authorization, authentication, or some other form of access control is not implemented or not implemented correctly, a user may be able to bypass on-chip protection mechanisms through the debug interface. Sometimes, designers choose not to expose the debug pins on the motherboard. Instead, they choose to hide these pins in the intermediate layers of the board. This is primarily done to work around the lack of debug authorization inside the chip. In such a scenario (without debug authorization), when the debug interface is exposed, chip internals are accessible to an attacker.
Last updated: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (2)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-41 | Port and I/O Device Access | SC | Directly mitigates exposure of on-chip debug and test interfaces by disabling or removing them. |
SR-10 | Inspection of Systems or Components | SR | Inspection of on-chip debug/test interfaces can identify tampering or unauthorized access that those interfaces enable. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-48970 | 1.9 | 9.3 | 0.0009 | 2024-11-14 |
CVE-2025-65821 | 1.5 | 7.5 | 0.0004 | 2025-12-10 |
CVE-2020-9285 | 1.4 | 6.8 | 0.0010 | 2022-10-20 |
CVE-2022-43096 | 1.4 | 6.8 | 0.0012 | 2022-11-17 |
CVE-2023-32666 | 1.4 | 7.2 | 0.0003 | 2024-03-14 |
CVE-2025-26409 | 1.4 | 6.8 | 0.0016 | 2025-02-11 |
CVE-2025-65822 | 1.4 | 6.8 | 0.0003 | 2025-12-10 |
CVE-2025-48468 | 1.3 | 6.4 | 0.0008 | 2025-06-24 |
CVE-2025-47819 | 1.3 | 6.4 | 0.0013 | 2025-06-27 |
CVE-2025-47822 | 1.3 | 6.4 | 0.0013 | 2025-06-27 |
CVE-2025-7213 | 1.3 | 6.4 | 0.0008 | 2025-07-09 |
CVE-2024-4231 | 1.2 | 4.6 | 0.0478 | 2024-05-14 |
CVE-2025-26408 | 1.2 | 6.1 | 0.0016 | 2025-02-11 |
CVE-2025-12114 | 1.1 | 5.5 | 0.0001 | 2025-10-23 |
CVE-2025-15083 | 0.4 | 2.0 | 0.0003 | 2025-12-25 |
CVE-2024-41692 | 0.0 | 0.0 | 0.0006 | 2024-07-26 |
CVE-2025-9709 | 0.0 | 0.0 | 0.0003 | 2025-09-05 |
CVE-2025-36755 | 0.0 | 0.0 | 0.0003 | 2025-12-12 |
CVE-2024-36319 | 0.0 | 0.0 | 0.0001 | 2026-02-12 |
CVE-2025-52533 | 0.0 | 0.0 | 0.0005 | 2026-02-12 |