CWE-1295 · Słabość
Debug Messages Revealing Unnecessary Information
- Abstrakcja
- Bazowa
- Status
- Niekompletny
- Dodano
- 31 maja 2020
- Ostatnia zmiana
- 30 kwietnia 2026
Opis
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".
Skutki
Confidentiality, Integrity, Availability, Access Control, Accountability, Authentication, Authorization, Non-Repudiation
Read Memory; Bypass Protection Mechanism; Gain Privileges or Assume Identity; Varies by Context
Zapobieganie
Implementation
Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.
Przykłady podatności
- CVE-2022-34364 Java-based SDK for TLS has a debug message with unnecessary information
- CVE-2021-25476 Digital Rights Management (DRM) capability for mobile platform leaks pointer information, simplifying ASLR bypass
- CVE-2020-24491 Processor generates debug message that contains sensitive information ("addresses of memory transactions").
- CVE-2017-18326 modem debug messages include cryptographic keys
Słabość nadrzędna
Pokrewna
Kiedy powstaje
- Implementation
Dotyczy
Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Not Technology-Specific
Źródła
Wpis z katalogu CWE 4.20.