CWE-488 Base Rascunho

Exposure of Data Element to Wrong Session

This vulnerability occurs when an application fails to properly isolate data between different user sessions, allowing information from one user's session to leak into another's.

Definição

What is CWE-488?

This vulnerability occurs when an application fails to properly isolate data between different user sessions, allowing information from one user's session to leak into another's.
This flaw typically happens when application components, like singleton objects or pooled resources, are incorrectly used to store user-specific data. For instance, in Java Servlets, a single instance often handles requests for all users simultaneously. If a developer stores user data in the Servlet's member fields instead of the proper request or session scope, one user's data can become visible to another user, creating a race condition. To prevent this, always store user state in the appropriate session context (like `HttpSession`) or within local method variables, never in shared object fields. Ensure your design clearly separates per-request data from shared application data, and understand the threading model of your framework's components.
Impacto no mundo real

Real-world CVEs caused by CWE-488

Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.

Como os atacantes a exploram

Trajeto do atacante passo a passo

  1. 1

    Identificar um caminho de código que trata input não confiável sem validação.

  2. 2

    Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.

  3. 3

    Entregar o payload através de um pedido normal e observar a reação da aplicação.

  4. 4

    Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.

Exemplo de código vulnerável

Vulnerable Java

The following Servlet stores the value of a request parameter in a member field and then later echoes the parameter value to the response output stream.

Vulnerável Java 
public class GuestBook extends HttpServlet {
  		String name;
  		protected void doPost (HttpServletRequest req, HttpServletResponse res) {
  			name = req.getParameter("name");
  			...
  			out.println(name + ", thanks for visiting!");
  		}
  }
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-488

  • Architecture and Design Protect the application's sessions from information leakage. Make sure that a session's data is not used or visible by other sessions.
  • Testing Use a static analysis tool to scan the code for information leakage vulnerabilities (e.g. Singleton Member Field).
  • Architecture and Design In a multithreading environment, storing user data in Servlet member fields introduces a data access race condition. Do not use member fields to store information in the Servlet.
Sinais de deteção

How to detect CWE-488

Automated Static Analysis High

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.)

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-488 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-488?

This vulnerability occurs when an application fails to properly isolate data between different user sessions, allowing information from one user's session to leak into another's.

Qual a gravidade do CWE-488?

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-488?

A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.

Como posso prevenir o CWE-488?

Protect the application's sessions from information leakage. Make sure that a session's data is not used or visible by other sessions. Use a static analysis tool to scan the code for information leakage vulnerabilities (e.g. Singleton Member Field).

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

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-488 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-488?

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

Fraquezas relacionadas

Weaknesses related to CWE-488

CWE-668 Pai

Exposure of Resource to Wrong Sphere

This vulnerability occurs when an application unintentionally makes a resource accessible to users or systems that should not have…

CWE-1189 Irmão

Improper Isolation of Shared Resources on System-on-a-Chip (SoC)

This vulnerability occurs when a System-on-a-Chip (SoC) fails to properly separate shared hardware resources between secure (trusted) and…

CWE-1282 Irmão

Assumed-Immutable Data is Stored in Writable Memory

This vulnerability occurs when data that should be permanent and unchangeable—like a bootloader, device IDs, or one-time configuration…

CWE-1327 Irmão

Binding to an Unrestricted IP Address

This vulnerability occurs when software or a service is configured to bind to the IP address 0.0.0.0 (or :: in IPv6), which acts as a…

CWE-1331 Irmão

Improper Isolation of Shared Resources in Network On Chip (NoC)

This vulnerability occurs when a Network on Chip (NoC) fails to properly separate its internal, shared resources—like buffers, switches,…

CWE-134 Irmão

Use of Externally-Controlled Format String

This vulnerability occurs when a program uses a format string from an untrusted, external source (like user input, a network packet, or a…

CWE-200 Irmão

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

Passing Mutable Objects to an Untrusted Method

This vulnerability occurs when a function receives a direct reference to mutable data, such as an object or array, instead of a safe copy…

CWE-375 Irmão

Returning a Mutable Object to an Untrusted Caller

This vulnerability occurs when a method directly returns a reference to its internal mutable data, allowing untrusted calling code to…

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