CWE-1244: Internal Asset Exposed to Unsafe Debug Access Level or State
The product uses physical debug or test interfaces with support for multiple access levels, but it assigns the wrong debug access level to an internal asset, providing unintended access to the asset from untrusted debug agents.
Last updated
Overview
Debug authorization can have multiple levels of access, defined such that different system internal assets are accessible based on the current authorized debug level. Other than debugger authentication (e.g., using passwords or challenges), the authorization can also be based on the system state or boot stage. For example, full system debug access might only be allowed early in boot after a system reset to ensure that previous session data is not accessible to the authenticated debugger.
Real-world CVEs
11 recorded CVEs are caused by CWE-1244 (Internal Asset Exposed to Unsafe Debug Access Level or State). The highest-severity and most recent are shown first. 2 new CWE-1244 CVEs have been recorded so far in 2026 (7 in 2025).
- CVE-2020-5372High · CVSS 8.6 · EPSS 61th2020-07-06
- CVE-2025-42878
Sensitive Data Exposure in SAP Web Dispatcher and Internet Communication Manager (ICM)
High · CVSS 8.2 · EPSS 30th2025-12-09 - CVE-2024-0114High · CVSS 8.1 · EPSS 12th2025-03-05
- CVE-2026-29642High · CVSS 7.8 · EPSS 1th2026-04-20
- CVE-2025-23252High · CVSS 7.5 · EPSS 26th2025-06-18
- CVE-2025-23337Medium · CVSS 6.7 · EPSS 5th2025-09-17
- CVE-2022-32259Medium · CVSS 6.5 · EPSS 52th2022-06-14
- CVE-2025-67862Medium · CVSS 6.0 · EPSS 4th2026-06-09
- CVE-2025-20238Medium · CVSS 6.0 · EPSS 5th2025-08-14
- CVE-2025-23302Medium · CVSS 4.2 · EPSS 3th2025-09-04
- CVE-2025-23301Medium · CVSS 4.2 · EPSS 3th2025-09-04
Common consequences
What can happen when CWE-1244 is exploited.
Read Memory
Affects: Confidentiality
If a protection mechanism does not ensure that internal assets have the correct debug access level during each boot stage or change in system state, an attacker could obtain sensitive information from the internal asset using a debugger.
Modify Memory
Affects: Integrity
Gain Privileges or Assume Identity, Bypass Protection Mechanism
Affects: Authorization, Access Control
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
Applies to
Technologies
How to prevent it
Practical mitigations for CWE-1244, grouped by where in the lifecycle they apply.
For security-sensitive assets accessible over debug/test interfaces, only allow trusted agents.
Effectiveness: High
Apply blinding [3] or masking techniques in strategic areas.
Effectiveness: Limited
Add shielding or tamper-resistant protections to the device, which increases the difficulty and cost for accessing debug/test interfaces.
Effectiveness: Limited
How to detect it
Manual Analysis
Check 2 devices for their passcode to authenticate access to JTAG/debugging ports. If the passcodes are missing or the same, update the design to fix and retest. Check communications over JTAG/debugging ports for encryption. If the communications are not encrypted, fix the design and retest.
Effectiveness: Moderate
Code examples
MITRE examples of the weakness in code.
The JTAG interface is used to perform debugging and provide CPU core access for developers. JTAG-access protection is implemented as part of the JTAG_SHIELD bit in the hw_digctl_ctrl register. This register has no default value at power up and is set only after the system boots from ROM and control is transferred to the user software.
Example
The default value of this register bit should be set to 1 to prevent the JTAG from being enabled at system reset.
This means that since the end user has access to JTAG at system reset and during ROM code execution before control is transferred to user software, a JTAG user can modify the boot flow and subsequently disclose all CPU information, including data-encryption keys.
The example code below is taken from the CVA6 processor core of the HACK@DAC'21 buggy OpenPiton SoC. Debug access allows users to access internal hardware registers that are otherwise not exposed for user access or restricted access through access control protocols. Hence, requests to enter debug mode are checked and authorized only if the processor has sufficient privileges. In addition, debug accesses are also locked behind password checkers. Thus, the processor enters debug mode only when the privilege level requirement is met, and the correct debug password is provided.
Vulnerable example
// check that we actually want to enter debug depending on the privilege level we are currently in
riscv::PRIV_LVL_M: begin
debug_mode_d = dcsr_q.ebreakm;
riscv::PRIV_LVL_U: begin
debug_mode_d = dcsr_q.ebreaku;
assign priv_lvl_o = (debug_mode_q || umode_i) ? riscv::PRIV_LVL_M : priv_lvl_q;
debug_mode_q <= debug_mode_d;Safe example
// check that we actually want to enter debug depending on the privilege level we are currently in
riscv::PRIV_LVL_M: begin
debug_mode_d = dcsr_q.ebreakm;
riscv::PRIV_LVL_U: begin
debug_mode_d = dcsr_q.ebreaku;
assign priv_lvl_o =
(debug_mode_q && umode_i) ? riscv::PRIV_LVL_M : priv_lvl_q;
debug_mode_q <= debug_mode_d;Illustrative examples
Real CVEs that MITRE cites as examples of this weakness.
- CVE-2019-18827 — After ROM code execution, JTAG access is disabled. But before the ROM code is executed, JTAG access is possible, allowing a user full system access. This allows a user to modify the boot flow and successfully bypass the secure-boot process.
Attack patterns
CAPEC attack patterns that exploit this weakness.
Frequently asked questions
Common questions about CWE-1244.
- What is CWE-1244?
- The product uses physical debug or test interfaces with support for multiple access levels, but it assigns the wrong debug access level to an internal asset, providing unintended access to the asset from untrusted debug agents.
- What CVEs are caused by CWE-1244?
- 11 recorded CVEs are attributed to CWE-1244, including CVE-2020-5372, CVE-2025-42878 and CVE-2024-0114.
- How do you prevent CWE-1244?
- For security-sensitive assets accessible over debug/test interfaces, only allow trusted agents.
- How is CWE-1244 detected?
- Manual Analysis: Check 2 devices for their passcode to authenticate access to JTAG/debugging ports. If the passcodes are missing or the same, update the design to fix and retest. Check communications over JTAG/debugging ports for encryption. If the communications are not encrypted, fix the design and retest.
- What are the consequences of CWE-1244?
- Exploiting CWE-1244 can lead to: Read Memory, Modify Memory, Gain Privileges or Assume Identity, Bypass Protection Mechanism.
- Is CWE-1244 actively exploited?
- 11 recorded CVEs are caused by CWE-1244; none are currently in CISA's KEV catalog of actively exploited flaws.
Sources
- [1]Multiple Vulnerabilities in Barco Clickshare: JTAG access is not permanently disabled
- [2]Attacks and Defenses for JTAG
- [3]Blindsight: Blinding EM Side-Channel Leakage using Built-In Fully Integrated Inductive Voltage Regulator (2018)
- [4]csr_regile.sv line 938 (2021)
- [5]Fix for csr_regfile.sv line 938 (2021)
References
- MITRE CWE definition (CWE-1244) (opens in a new tab)
- CWE-1244 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Track CWE-1244 CVEs
Get an alert when a new CWE-1244 CVE affects your products, with AI-written analysis and remediation steps.