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 Incomplete
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.
Definition
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.
Real-world impact
Real-world CVEs caused by CWE-613
No public CVE references are linked to this CWE in MITRE's catalog yet.
How attackers exploit it
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 4
Iterate until the response leaks data, executes attacker code, or escalates privileges.
Vulnerable code example
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> Secure code example
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.
Prevention checklist
How to prevent CWE-613
- Implementation Set sessions/credentials expiration date.
Detection signals
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.
Frequently asked questions What is CWE-613?
How serious is CWE-613?
What languages or platforms are affected by CWE-613?
How can I prevent CWE-613?
How does Plexicus detect and fix CWE-613?
Where can I learn more about CWE-613?
Frequently asked questions
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.
How serious is CWE-613?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-613?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-613?
Set sessions/credentials expiration date.
How does Plexicus detect and fix CWE-613?
Plexicus's SAST engine matches the data-flow signature for CWE-613 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-613?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/613.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
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 Sibling
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 Sibling
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 Sibling
Double Free
A double free vulnerability occurs when a program mistakenly calls the 'free()' function twice on the same block of memory.
CWE-416 Sibling
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 Sibling
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 Sibling
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 Can precede
Improper Authentication
Improper Authentication occurs when a system fails to properly verify a user's claimed identity, allowing access without sufficient proof…
Ready to validate what matters?
Ready to validate what matters?
Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.