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.)
CWE-539 Variante Incompleto
Use of Persistent Cookies Containing Sensitive Information
This vulnerability occurs when a web application stores sensitive data, like authentication details or personal information, within persistent cookies that remain on a user's device.
Definición
What is CWE-539?
This vulnerability occurs when a web application stores sensitive data, like authentication details or personal information, within persistent cookies that remain on a user's device.
Cookies are small pieces of data set by a web application and stored locally in a user's browser. While they are essential for maintaining state—like keeping a user logged in or remembering site preferences—they become a security risk when sensitive information is written directly into a cookie that is saved to disk. Unlike session cookies, which are deleted when the browser closes, persistent cookies remain on the hard drive for a defined period, making the sensitive data they contain accessible long-term.
Storing sensitive data such as usernames, passwords, session tokens, or personal details in a persistent cookie exposes it to theft or misuse. Attackers can extract these cookies from browser files or through cross-site scripting (XSS) attacks, potentially leading to account takeover or privacy violations. Developers should instead use persistent cookies only for non-sensitive identifiers, storing the actual sensitive data securely on the server side where it can be properly protected.
Impacto en el mundo real
Real-world CVEs caused by CWE-539
Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
Identifica una ruta de código que maneje entrada no confiable sin validación.
- 2
Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.
- 3
Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.
- 4
Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.
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.
// 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
// 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-539
- Architecture and Design Do not store sensitive information in persistent cookies.
Señales de detección
How to detect CWE-539
CWE-539
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Preguntas frecuentes ¿Qué es CWE-539?
¿Qué gravedad tiene CWE-539?
¿Qué lenguajes o plataformas se ven afectados por CWE-539?
¿Cómo puedo prevenir CWE-539?
¿Cómo detecta y corrige Plexicus CWE-539?
¿Dónde puedo aprender más sobre CWE-539?
Frequently asked questions
¿Qué es CWE-539?
This vulnerability occurs when a web application stores sensitive data, like authentication details or personal information, within persistent cookies that remain on a user's device.
¿Qué gravedad tiene CWE-539?
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-539?
MITRE no ha especificado plataformas afectadas para esta CWE — puede aplicar a la mayoría de los stacks de aplicaciones.
¿Cómo puedo prevenir CWE-539?
Do not store sensitive information in persistent cookies.
¿Cómo detecta y corrige Plexicus CWE-539?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-539 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-539?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/539.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-539
CWE-552 Padre
Files or Directories Accessible to External Parties
This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.
CWE-219 Hermano
Storage of File with Sensitive Data Under Web Root
This vulnerability occurs when an application saves sensitive files, such as configuration data or private keys, inside the web server's…
CWE-220 Hermano
Storage of File With Sensitive Data Under FTP Root
This vulnerability occurs when an application saves sensitive files, such as configuration or user data, within the directory served by an…
CWE-527 Hermano
Exposure of Version-Control Repository to an Unauthorized Control Sphere
This vulnerability occurs when a version control repository, like Git or SVN, is accidentally placed in a location accessible to…
CWE-528 Hermano
Exposure of Core Dump File to an Unauthorized Control Sphere
This vulnerability occurs when an application creates a core dump file (a snapshot of memory at the time of a crash) and places it in a…
CWE-529 Hermano
Exposure of Access Control List Files to an Unauthorized Control Sphere
This vulnerability occurs when an application stores sensitive access control list (ACL) files in a location that is accessible to…
CWE-530 Hermano
Exposure of Backup File to an Unauthorized Control Sphere
This vulnerability occurs when backup or temporary files are stored in locations that unauthorized users can access, such as web…
CWE-553 Hermano
Command Shell in Externally Accessible Directory
This vulnerability occurs when a command shell script is placed in a web-accessible directory, such as /cgi-bin/. Attackers can directly…
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.