CWE · MITRE source
CWE-1295Debug Messages Revealing Unnecessary Information
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
Debug messages are messages that help troubleshoot an issue by revealing the internal state of the system. For example, debug data in design can be exposed through internal memory array dumps or boot logs through interfaces like UART via TAP commands, scan chain, etc. Thus, the more information contained in a debug message, the easier it is to debug. However, there is also the risk of revealing information that could help an attacker either decipher a vulnerability, and/or gain a better understanding of the system. Thus, this extra information could lower the "security by obscurity" factor. While "security by obscurity" alone is insufficient, it can help as a part of "Defense-in-depth".
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: full · 7 mapping(s) from 6 framework(s): ATT&CK 2 (partial) · ASVS 5.0 1 (full) · CAPEC 1 (partial) · STIG windows 10 1 (partial) · STIG windows server 2016 1 (partial) · STIG windows server 2019 1 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
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-2023-5392 | 5.5 | 7.5 | 0.0048 | 2024-04-11 |
CVE-2024-38516 | 5.5 | 8.8 | 0.0051 | 2024-06-25 |
CVE-2024-45784 | 5.5 | 7.5 | 0.0129 | 2024-11-15 |
CVE-2025-31001 | 5.5 | 7.5 | 0.0048 | 2025-04-01 |
CVE-2021-31412 | 3.5 | 5.3 | 0.0132 | 2021-06-24 |
CVE-2021-25476 | 3.5 | 4.1 | 0.0010 | 2021-10-06 |
CVE-2022-34364 | 3.5 | 4.4 | 0.0019 | 2023-02-10 |
CVE-2023-4215 | 3.5 | 6.5 | 0.0046 | 2023-10-17 |
CVE-2023-28077 | 3.5 | 4.4 | 0.0018 | 2024-02-10 |
CVE-2024-27179 | 3.5 | 4.7 | 0.0026 | 2024-06-14 |
CVE-2024-11217 UPD | 3.5 | 4.9 | 0.0036 | 2024-11-15 |
CVE-2025-2877 | 3.5 | 6.5 | 0.0038 | 2025-03-28 |
CVE-2025-12910 | 3.5 | 6.2 | 0.0009 | 2025-11-08 |
CVE-2025-46775 | 3.5 | 5.5 | 0.0014 | 2025-11-18 |
CVE-2025-20643 | 1.6 | 3.9 | 0.0009 | 2025-02-03 |
CVE-2022-27597 | 1.5 | 2.7 | 0.0066 | 2023-03-29 |
CVE-2025-2469 | 1.5 | 3.7 | 0.0034 | 2025-04-10 |
CVE-2025-35031 | 1.5 | 3.3 | 0.0013 | 2025-09-29 |