CWE-298: Improper Validation of Certificate Expiration Skip to content

Security weakness

CWE-298 Improper Validation of Certificate Expiration

A variant-level weakness that can lead to data, pages or code changed and sign-in that does not protect. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-298?

Improper Validation of Certificate Expiration: A certificate expiration is not validated or is incorrectly validated.

Business impact

What CWE-298 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Other

Authentication

Sign-in that does not protect

Weak or bypassable authentication lets the wrong people sign in as someone else.

  • Other

Free security check

Is CWE-298 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-298

Improper Validation of Certificate Expiration

A certificate expiration is not validated or is incorrectly validated.

Weakness ID
CWE-298
Type
Variant
Status
Draft
Likelihood of exploit
Low
Introduced during
Implementation

Prevention

How to fix CWE-298, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • Check for expired certificates and provide the user with adequate information about the nature of the problem and how to proceed.
  2. 02

    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.

Detection and evidence

How CWE-298 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • Automated Static AnalysisAutomated 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.

Real vulnerabilities it caused

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

How we fix it

From finding to fixed: how Codefreex closes CWE-298

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-298: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-298?

CWE-298, “Improper Validation of Certificate Expiration”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. A certificate expiration is not validated or is incorrectly validated.

How serious is CWE-298?

MITRE rates the likelihood of exploit as Low. It can affect integrity, other, authentication, with impacts such as other. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-298?

Check for expired certificates and provide the user with adequate information about the nature of the problem and how to proceed. 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.

Can Codefreex check my site for CWE-298?

Yes. A senior engineer reviews your site, store or app for CWE-298 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-298 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.