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.

Definição

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 no 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

Como os atacantes a exploram

Trajeto do atacante passo a passo

  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.

Exemplo de código vulnerável

Vulnerable pseudo

A MITRE não publicou um exemplo de código para este CWE. O padrão abaixo é ilustrativo — consulte os Recursos para referências canónicas.

Vulnerável pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Exemplo 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 verificação de prevenção

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.
Sinais de deteção

How to detect CWE-1295

SAST High

Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.

DAST Moderate

Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.

Runtime Moderate

Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.

Code review Moderate

Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-1295 e abre um PR de correção em menos de 60 segundos.

O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o CWE-1295?

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

Qual a gravidade do CWE-1295?

A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.

Que linguagens ou plataformas são afetadas pelo CWE-1295?

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

Como posso prevenir o CWE-1295?

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

Como é que o Plexicus deteta e corrige o CWE-1295?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1295 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.

Onde posso saber mais sobre o CWE-1295?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/1295.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-1295

CWE-200 Pai

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 Irmão

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 Irmão

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 Irmão

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 Irmão

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 Irmão

Observable Discrepancy

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

CWE-209 Irmão

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 Irmão

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 Irmão

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

Pronto quando você estiver

Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.

O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.

Começar grátis Reservar uma demo