CWE-1258: Exposure of Sensitive System Information Due to Uncleared Debug Information
The hardware does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations, when debug mode is entered.
Last updated
Overview
Security sensitive values, keys, intermediate steps of cryptographic operations, etc. are stored in temporary registers in the hardware. If these values are not cleared when debug mode is entered they may be accessed by a debugger allowing sensitive information to be accessible by untrusted parties.
Real-world CVEs
16 recorded CVEs are caused by CWE-1258 (Exposure of Sensitive System Information Due to Uncleared Debug Information). The highest-severity and most recent are shown first. 8 new CWE-1258 CVEs have been recorded so far in 2026 (2 in 2025).
- CVE-2024-36912
Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl
Critical · CVSS 9.6 · EPSS 62th2024-05-30 - CVE-2024-36913
Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails
Critical · CVSS 9.3 · EPSS 52th2024-05-30 - CVE-2026-66432
WordPress WPJAM Basic plugin <= 7.0.2.1 - Sensitive Data Exposure vulnerability
High · CVSS 7.5 · EPSS 36th2026-08-13 - CVE-2026-52696
WordPress JetBlog plugin <= 2.4.8 - Sensitive Data Exposure vulnerability
High · CVSS 7.5 · EPSS 15th2026-06-17 - CVE-2022-39292
Exposure of sensitive Slack webhook URLs in debug logs and traces
High · CVSS 7.5 · EPSS 59th2022-10-10 - CVE-2022-31162
Slack Morphism for Rust before 0.41.0 can accidentally leak Slack OAuth client information in application debug logs
High · CVSS 7.5 · EPSS 60th2022-07-21 - CVE-2023-48308
Calendar app returns full stacktrace when an error happens while editing appointment
Medium · CVSS 6.5 · EPSS 46th2023-12-21 - CVE-2022-43666Medium · CVSS 5.5 · EPSS 12th2023-11-14
- CVE-2025-32257
WordPress 1 Click WordPress Migration plugin <= 2.5.7 - Sensitive Data Exposure vulnerability
Medium · CVSS 5.3 · EPSS 58th2025-04-04 - CVE-2026-65127Medium · CVSS 4.9 · EPSS 21th2026-09-22
- CVE-2026-26948Medium · CVSS 4.9 · EPSS 24th2026-03-18
- CVE-2025-26482Medium · CVSS 4.9 · EPSS 23th2025-09-25
Showing 12 of 16 recorded CWE-1258 CVEs. Get an alert for each new one, with AI-written analysis and fixes.
Monitor these CVEsCommon consequences
What can happen when CWE-1258 is exploited.
Read Memory
Affects: Confidentiality
Bypass Protection Mechanism
Affects: Access Control
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
How to prevent it
Practical mitigations for CWE-1258, grouped by where in the lifecycle they apply.
Whenever debug mode is enabled, all registers containing sensitive assets must be cleared.
Code examples
MITRE examples of the weakness in code.
A cryptographic core in a System-On-a-Chip (SoC) is used for cryptographic acceleration and implements several cryptographic operations (e.g., computation of AES encryption and decryption, SHA-256, HMAC, etc.). The keys for these operations or the intermediate values are stored in registers internal to the cryptographic core. These internal registers are in the Memory Mapped Input Output (MMIO) space and are blocked from access by software and other untrusted agents on the SoC. These registers are accessible through the debug and test interface.
The following code example is extracted from the AES wrapper module, aes1_wrapper, of the Hack@DAC'21 buggy OpenPiton System-on-Chip (SoC). Within this wrapper module are four memory-mapped registers: core_key, core_key0, core_key1, and core_key2. Core_key0, core_key1, and core_key2 hold encryption/decryption keys. The core_key register selects a key and sends it to the underlying AES module to execute encryption/decryption operations.
Debug mode in processors and SoCs facilitates design debugging by granting access to internal signal/register values, including physical pin values of peripherals/core, fabric bus data transactions, and inter-peripheral registers. Debug mode allows users to gather detailed, low-level information about the design to diagnose potential issues. While debug mode is beneficial for diagnosing processors or SoCs, it also introduces a new attack surface for potential attackers. For instance, if an attacker gains access to debug mode, they could potentially read any content transmitted through the fabric bus or access encryption/decryption keys stored in cryptographic peripherals.
Therefore, it is crucial to clear the contents of secret registers upon entering debug mode. In the provided example of flawed code below, when debug_mode_i is activated, the register core_key0 is set to zero to prevent AES key leakage during debugging. However, this protective measure is not applied to the core_key1 register [1], leaving its contents uncleared during debug mode. This oversight enables a debugger to access sensitive information. Failing to clear sensitive data during debug mode may lead to unauthorized access to secret keys and compromise system security.
Vulnerable example
assign core_key0 = debug_mode_i ? 'b0 : {
assign core_key1 = {
key_reg0[7],
key_reg1[7],
key_reg1[6],
key_reg1[5],
key_reg1[4],
key_reg1[3],
key_reg1[2],
key_reg1[1],
key_reg1[0]};Safe example
assign core_key0 = debug_mode_i ? 'b0 : {
debug_mode_i ? 'b0 :
key_reg0[7],
key_reg1[7],To address the issue, it is essential to ensure that the register is cleared and zeroized after activating debug mode on the SoC. In the correct implementation illustrated in the good code below, core_keyx registers are set to zero when debug mode is activated [2].
Illustrative examples
Real CVEs that MITRE cites as examples of this weakness.
- CVE-2021-33080 — Uncleared debug information in memory accelerator for SSD product exposes sensitive system information
- CVE-2022-31162 — Rust library leaks Oauth client details in application debug logs
Attack patterns
CAPEC attack patterns that exploit this weakness.
Frequently asked questions
Common questions about CWE-1258.
- What is CWE-1258?
- The hardware does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations, when debug mode is entered.
- What CVEs are caused by CWE-1258?
- 16 recorded CVEs are attributed to CWE-1258, including CVE-2024-36912, CVE-2024-36913 and CVE-2026-66432.
- How do you prevent CWE-1258?
- Whenever debug mode is enabled, all registers containing sensitive assets must be cleared.
- What are the consequences of CWE-1258?
- Exploiting CWE-1258 can lead to: Read Memory, Bypass Protection Mechanism.
- Is CWE-1258 actively exploited?
- 16 recorded CVEs are caused by CWE-1258; none are currently in CISA's KEV catalog of actively exploited flaws.
Sources
- [1]Bad Code aes1_wrapper.sv (2021)
- [2]Good Code aes1_wrapper.sv (2021)
References
- MITRE CWE definition (CWE-1258) (opens in a new tab)
- CWE-1258 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-1258 CVEs
Get an alert when a new CWE-1258 CVE affects your products, with AI-written analysis and remediation steps.