CWE-298 Improper Validation of Certificate Expiration

A certificate expiration is not validated or is incorrectly validated.

• Integrity, Other: Other — The data read from the system vouched for by the expired certificate may be flawed due to malicious spoofing. • Authentication, Other: Other — Trust may be assigned to certificates that have been abandoned due to age.

• [Architecture and Design] Check for expired certificates and provide the user with adequate information about the nature of the problem and how to proceed. • [Implementation] If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the expiration.

• Automated Static Analysis: 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.)

• CVE-2025-4384: product does not verify that a certificate has expired • CVE-2007-3564: web library product does not verify that a certificate has expired • CVE-2007-6746: IRC product does not check the expiration date of the X.509 certificate