CWE-1295 Base Incompleto

Debug Messages Revealing Unnecessary Information

The product's debug messages or logs expose excessive internal system details, potentially revealing sensitive information that could aid an attacker.

Definición

What is CWE-1295?

The product's debug messages or logs expose excessive internal system details, potentially revealing sensitive information that could aid an attacker.
Debug messages are essential for developers to diagnose issues by showing the system's internal state, such as memory dumps, boot logs, or low-level hardware data exposed through interfaces like UART or scan chains. While more detailed logs make troubleshooting easier, they also risk exposing information that could help an attacker identify vulnerabilities or understand the system's architecture. Relying solely on hiding information (security through obscurity) is not a safe strategy, but it can be a useful layer within a broader defense-in-depth approach. Unnecessary details in debug output lower this protective layer, making it easier for attackers to piece together an attack even when other security controls are in place.
Impacto en el mundo real

Real-world CVEs caused by CWE-1295

  • 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

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    This example here shows how an attacker can take advantage of unnecessary information in debug messages.

  2. 2

    Example 1: Suppose in response to a Test Access Port (TAP) chaining request the debug message also reveals the current TAP hierarchy (the full topology) in addition to the success/failure message.

  3. 3

    Example 2: In response to a password-filling request, the debug message, instead of a simple Granted/Denied response, prints an elaborate message, "The user-entered password does not match the actual password stored in ."

  4. 4

    The result of the above examples is that the user is able to gather additional unauthorized information about the system from the debug messages.

  5. 5

    The solution is to ensure that Debug messages do not reveal additional details.

Ejemplo de código vulnerable

Vulnerable pseudo

MITRE no ha publicado un ejemplo de código para esta CWE. El patrón siguiente es ilustrativo — consulta Recursos para referencias canónicas.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Ejemplo de código seguro

Secure pseudo

Seguro pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención

How to prevent CWE-1295

  • Implementation Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.
Señales de detección

How to detect CWE-1295

SAST High

Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.

DAST Moderate

Ejecuta pruebas dinámicas de seguridad de aplicaciones (DAST) contra el endpoint en vivo.

Runtime Moderate

Vigila los logs en tiempo de ejecución para detectar trazas de excepción inusuales, entradas malformadas o intentos de bypass de autorización.

Code review Moderate

Revisión de código: marca cualquier código nuevo que maneje entrada desde esta superficie sin usar los helpers validados del framework.

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-1295 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-1295?

The product's debug messages or logs expose excessive internal system details, potentially revealing sensitive information that could aid an attacker.

¿Qué gravedad tiene CWE-1295?

MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.

¿Qué lenguajes o plataformas se ven afectados por CWE-1295?

MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, Not Technology-Specific.

¿Cómo puedo prevenir CWE-1295?

Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.

¿Cómo detecta y corrige Plexicus CWE-1295?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-1295 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.

¿Dónde puedo aprender más sobre CWE-1295?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/1295.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-1295

CWE-200 Padre

Exposure of Sensitive Information to an Unauthorized Actor

This weakness occurs when an application unintentionally reveals sensitive data to someone who shouldn't have access to it.

CWE-1258 Hermano

Exposure of Sensitive System Information Due to Uncleared Debug Information

This vulnerability occurs when hardware fails to erase sensitive data like cryptographic keys and intermediate values before entering…

CWE-1273 Hermano

Device Unlock Credential Sharing

This vulnerability occurs when the secret keys or passwords required to unlock a device's hidden features are shared between multiple…

CWE-1431 Hermano

Driving Intermediate Cryptographic State/Results to Hardware Module Outputs

This vulnerability occurs when a hardware cryptographic module leaks sensitive internal data through its output channels. Instead of only…

CWE-201 Hermano

Insertion of Sensitive Information Into Sent Data

This vulnerability occurs when an application sends data to an external party, but accidentally includes sensitive information—like…

CWE-203 Hermano

Observable Discrepancy

This vulnerability occurs when an application responds differently to unauthorized users based on internal conditions. Attackers can…

CWE-209 Hermano

Generation of Error Message Containing Sensitive Information

This vulnerability occurs when an application reveals sensitive details about its internal systems, user data, or environment within error…

CWE-213 Hermano

Exposure of Sensitive Information Due to Incompatible Policies

This vulnerability occurs when a system's data handling aligns with the developer's security rules but accidentally reveals information…

CWE-215 Hermano

Insertion of Sensitive Information Into Debugging Code

This vulnerability occurs when developers embed sensitive data, such as passwords or API keys, within debugging statements like logs or…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo