Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
CWE-324 Base Draft
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 so dramatically increases the security risk by giving…
Definition
What is CWE-324?
This vulnerability occurs when an application continues to use a cryptographic key or password after its designated expiration date. Doing so dramatically increases the security risk by giving attackers more time to discover or crack the key.
Using a key past its expiration date significantly weakens your security posture. While an expired key isn't automatically compromised, the longer it remains active, the greater the chance it could be discovered through brute-force attacks, leaks, or advancing computational power. This extended usage window directly undermines the cryptographic strength you initially implemented.
To maintain robust security, you must proactively manage key lifecycles. Establish and enforce a key rotation schedule that replaces keys within a timeframe appropriate for their algorithm and bit strength. Regular rotation limits the potential damage if a key is exposed and aligns with security best practices for data protection.
Real-world impact
Real-world CVEs caused by CWE-324
-
Picture Archiving and Communication System (PACS) system for hospitals uses a cryptographic key or password past its expiration date
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 C
The following code attempts to verify that a certificate is valid.
if (cert = SSL_get_peer_certificate(ssl)) {
foo=SSL_get_verify_result(ssl);
if ((X509_V_OK==foo) || (X509_V_ERRCERT_NOT_YET_VALID==foo))
```
//do stuff*
} 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-324
- Architecture and Design Adequate consideration should be put in to the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.
Detection signals
How to detect CWE-324
Run dynamic application security testing against the live endpoint.
Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.
Code review: flag any new code that handles input from this surface without using the validated framework helpers.
CWE-324
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-324?
How serious is CWE-324?
What languages or platforms are affected by CWE-324?
How can I prevent CWE-324?
How does Plexicus detect and fix CWE-324?
Where can I learn more about CWE-324?
Frequently asked questions
What is CWE-324?
This vulnerability occurs when an application continues to use a cryptographic key or password after its designated expiration date. Doing so dramatically increases the security risk by giving attackers more time to discover or crack the key.
How serious is CWE-324?
MITRE rates the likelihood of exploit as Low — exploitation is uncommon, but the weakness should still be fixed when discovered.
What languages or platforms are affected by CWE-324?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-324?
Adequate consideration should be put in to the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.
How does Plexicus detect and fix CWE-324?
Plexicus's SAST engine matches the data-flow signature for CWE-324 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-324?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/324.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-324
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-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-613 Sibling
Insufficient Session Expiration
Insufficient session expiration occurs when an application allows old session tokens or IDs to remain valid for too long, letting…
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.
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.