CWE-1295
Debug Messages Revealing Unnecessary Information
Incomplete
2020-08-20
00h00 +00:00
00h00 +00:00
2025-12-11
00h00 +00:00
00h00 +00:00
Notificaciones para un CWE
Manténgase informado sobre cualquier cambio en un CWE específico.
Nombre: Debug Messages Revealing Unnecessary Information
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
Informaciones generales
Modos de introducción
ImplementationPlataformas aplicables
Lenguaje
Class: Not Language-Specific (Undetermined)Sistemas operativos
Class: Not OS-Specific (Undetermined)Arquitecturas
Class: Not Architecture-Specific (Undetermined)Tecnologías
Class: Not Technology-Specific (Undetermined)Consecuencias comunes
| Alcance | Impacto | Probabilidad |
|---|---|---|
| Confidentiality Integrity Availability Access Control Accountability Authentication Authorization Non-Repudiation | Read Memory, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Varies by Context | Medium |
Ejemplos observados
| Referencias | Descripción |
|---|---|
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 |
Mitigaciones potenciales
Phases : ImplementationEnsure that a debug message does not reveal any unnecessary information during the debug process for the intended response.
Métodos de detección
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)Notas de mapeo de vulnerabilidades
Justificación : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.Comentario : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Patrones de ataque relacionados
| CAPEC-ID | Nombre del patrón de ataque |
|---|---|
| CAPEC-121 | Exploit Non-Production Interfaces
|
Referencias
REF-1112
Android Security Bulletin - December 2018https://source.android.com/docs/security/bulletin/2018-12-01
Envío
| Nombre | Organización | Fecha | Fecha de lanzamiento | Version |
|---|---|---|---|---|
| Parbati Kumar Manna, Hareesh Khattri, Arun Kanuparthi | Intel Corporation | 4.2 |
Modificaciones
| Nombre | Organización | Fecha | Comentario |
|---|---|---|---|
| CWE Content Team | MITRE | updated Observed_Examples, Related_Attack_Patterns, Relationships | |
| CWE Content Team | MITRE | updated References | |
| CWE Content Team | MITRE | updated Observed_Examples, References, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated References | |
| CWE Content Team | MITRE | updated Detection_Factors, Weakness_Ordinalities |
