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-613 Base Incomplet
Insufficient Session Expiration
Insufficient session expiration occurs when an application allows old session tokens or IDs to remain valid for too long, letting attackers reuse them to gain unauthorized access.
Définition
What is CWE-613?
Insufficient session expiration occurs when an application allows old session tokens or IDs to remain valid for too long, letting attackers reuse them to gain unauthorized access.
This vulnerability happens because sessions don't expire quickly or securely enough. Common causes include overly long timeout periods, missing logout functions that invalidate tokens on the server, or sessions that persist indefinitely after a user closes their browser. Attackers can steal these lingering session credentials through techniques like cross-site scripting or session fixation, then impersonate legitimate users long after they've left the application.
To prevent this, enforce short, absolute session timeouts, implement secure logout that destroys server-side session data, and tie sessions to client attributes like IP address or user agent. Regularly rotate session IDs after login or privilege changes. While SAST tools can detect the pattern, Plexicus uses AI to analyze session management flows and suggest precise code fixes—like implementing proper invalidation logic—saving hours of manual review and reducing risk across your entire application stack.
Impact réel
Real-world CVEs caused by CWE-613
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 Java
The following snippet was taken from a J2EE web.xml deployment descriptor in which the session-timeout parameter is explicitly defined (the default value depends on the container). In this case the value is set to -1, which means that a session will never expire.
<web-app>
[...snipped...]
<session-config>
<session-timeout>-1</session-timeout>
</session-config>
</web-app> 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-613
- Implementation Set sessions/credentials expiration date.
Signaux de détection
How to detect CWE-613
CWE-613
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-613 ?
Quelle est la gravité de CWE-613 ?
Quels langages ou plateformes sont affectés par CWE-613 ?
Comment puis-je prévenir CWE-613 ?
Comment Plexicus détecte et corrige CWE-613 ?
Où puis-je en savoir plus sur CWE-613 ?
Frequently asked questions
Qu'est-ce que CWE-613 ?
Insufficient session expiration occurs when an application allows old session tokens or IDs to remain valid for too long, letting attackers reuse them to gain unauthorized access.
Quelle est la gravité de CWE-613 ?
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-613 ?
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-613 ?
Set sessions/credentials expiration date.
Comment Plexicus détecte et corrige CWE-613 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-613 à 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-613 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/613.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-613
CWE-672 Parent
Operation on a Resource after Expiration or Release
This vulnerability occurs when a program continues to use a resource—like memory, a file handle, or a network connection—after it has been…
CWE-298 Frère
Improper Validation of Certificate Expiration
This vulnerability occurs when an application fails to properly check if a digital certificate has expired, potentially trusting…
CWE-324 Frère
Use of a Key Past its Expiration Date
This vulnerability occurs when an application continues to use a cryptographic key or password after its designated expiration date. Doing…
CWE-415 Frère
Double Free
A double free vulnerability occurs when a program mistakenly calls the 'free()' function twice on the same block of memory.
CWE-416 Frère
Use After Free
Use After Free happens when a program continues to use a pointer to a memory location after that memory has been freed. This can lead to…
CWE-825 Frère
Expired Pointer Dereference
This vulnerability occurs when a program tries to use a pointer that still points to a memory location that has already been freed or…
CWE-910 Frère
Use of Expired File Descriptor
This vulnerability occurs when a program attempts to use a file descriptor after it has been closed, treating it as if it were still valid.
CWE-287 Peut précéder
Improper Authentication
Improper Authentication occurs when a system fails to properly verify a user's claimed identity, allowing access without sufficient proof…
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.