BaseDraft

CWE-324Use of a Key Past its Expiration Date

Category: other

Description

The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key. While the expiration of keys does not necessarily ensure that they are compromised, it is a significant concern that keys which remain in use for prolonged periods of time have a decreasing probability of integrity. For this reason, it is important to replace keys within a period of time proportional to their strength.

Common consequences· 1

  • Access Control — Bypass Protection Mechanism, Gain Privileges or Assume Identity
    The cryptographic key in question may be compromised, providing a malicious user with a method for authenticating as the victim.

Potential mitigations· 1

  • [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.

References

  1. https://cwe.mitre.org/data/definitions/324.html

(incoming)4

TypeTargetConfidenceTier
VulnerabilityCVE-2025-2291cve-2025-22910%live
VulnerabilityCVE-2025-31123cve-2025-311230%live
VulnerabilityCVE-2025-33012cve-2025-330120%live
KEVEntryIGEL OS Use of a Key Past its Expiration Date Vulnerabilitykev-cve-2025-478270%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Use of Hard-coded Cryptographic Key
CWE
Inadequate Encryption Strength
CWE
Use of Weak Credentials
CWE
Use of a Broken or Risky Cryptographic Algorithm
CWE
Use of Default Cryptographic Key
CWE
Operation on a Resource after Expiration or Release
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.