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 Incomplet
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.
Définition
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.
Impact réel
Real-world CVEs caused by CWE-539
Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 1
Identifier un chemin de code qui traite des entrées non fiables sans validation.
- 2
Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.
- 3
Délivrer la charge utile via une requête normale et observer la réaction de l'application.
- 4
Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.
Exemple de code vulnérable
Vulnerable pseudo
MITRE n'a pas publié d'exemple de code pour ce CWE. Le motif ci-dessous est illustratif — voir Ressources pour les références canoniques.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Exemple de code sécurisé
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.
Liste de contrôle de prévention
How to prevent CWE-539
- Architecture and Design Do not store sensitive information in persistent cookies.
Signaux de détection
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.
Questions fréquentes Qu'est-ce que CWE-539 ?
Quelle est la gravité de CWE-539 ?
Quels langages ou plateformes sont affectés par CWE-539 ?
Comment puis-je prévenir CWE-539 ?
Comment Plexicus détecte et corrige CWE-539 ?
Où puis-je en savoir plus sur CWE-539 ?
Frequently asked questions
Qu'est-ce que 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.
Quelle est la gravité de CWE-539 ?
MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.
Quels langages ou plateformes sont affectés par CWE-539 ?
MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.
Comment puis-je prévenir CWE-539 ?
Do not store sensitive information in persistent cookies.
Comment Plexicus détecte et corrige CWE-539 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-539 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.
Où puis-je en savoir plus sur CWE-539 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/539.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-539
CWE-552 Parent
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 Frère
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 Frère
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 Frère
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 Frère
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 Frère
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 Frère
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 Frère
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…
Prêt à valider l'essentiel ?
Prêt à valider ce qui compte.
Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.