CWE-296: Improper Following of a Certificate's Chain of Skip to content

Security weakness

CWE-296 Improper Following of a Certificate’s Chain of Trust

A base-level weakness that can lead to private data exposed, data, pages or code changed and downtime and lost sales. 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-296?

Improper Following of a Certificate’s Chain of Trust: The product does not follow, or incorrectly follows, the chain of trust for a certificate back to a trusted root certificate.

Business impact

What CWE-296 could cost your business

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

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • Gain Privileges or Assume Identity
  • Execute Unauthorized Code or Commands

Integrity

Data, pages or code changed

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

  • Gain Privileges or Assume Identity
  • Execute Unauthorized Code or Commands

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • Gain Privileges or Assume Identity
  • Execute Unauthorized Code or Commands

Access Control

Accounts and admin areas exposed

Logins and permission checks can be bypassed, putting admin and customer accounts at risk.

  • Gain Privileges or Assume Identity
  • Execute Unauthorized Code or Commands

Non-Repudiation

Actions you cannot trace

Changes can happen without a reliable record, which slows incident response and compliance work.

  • Hide Activities

Free security check

Is CWE-296 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-296

Improper Following of a Certificate’s Chain of Trust

The product does not follow, or incorrectly follows, the chain of trust for a certificate back to a trusted root certificate.

There are several ways in which the chain of trust might be broken, including but not limited to:

Any certificate in the chain is self-signed, unless it is the root.

Not every intermediate certificate is checked, starting from the original certificate all the way up to the root certificate.

An intermediate, CA-signed certificate does not have the expected Basic Constraints or other important extensions.

The root certificate has been compromised or authorized to the wrong party.

Weakness ID
CWE-296
Type
Base
Status
Draft
Likelihood of exploit
Low
Applies to
Web Based
Introduced during
Implementation

Prevention

How to fix CWE-296, phase by phase

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

  1. 01

    Architecture and Design

    • Ensure that proper certificate checking is included in the system design.
  2. 02

    Implementation

    • Understand, and properly implement all checks necessary to ensure the integrity of certificate trust integrity.
    • If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the full chain of trust.

Detection and evidence

How CWE-296 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-2016-2402Server allows bypass of certificate pinning by sending a chain of trust that includes a trusted CA that is not pinned.
  • CVE-2008-4989Verification function trusts certificate chains in which the last certificate is self-signed.
  • CVE-2012-5821Chain: Web browser uses a TLS-related function incorrectly, preventing it from verifying that a server’s certificate is signed by a trusted certification authority (CA).
  • CVE-2009-3046Web browser does not check if any intermediate certificates are revoked.
  • CVE-2009-0265Chain: DNS server does not correctly check return value from the OpenSSL EVP_VerifyFinal function allows bypass of validation of the certificate chain.
  • CVE-2009-0124Chain: incorrect check of return value from the OpenSSL EVP_VerifyFinal function allows bypass of validation of the certificate chain.

How we fix it

From finding to fixed: how Codefreex closes CWE-296

  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-296: FAQs

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

What is CWE-296?

CWE-296, “Improper Following of a Certificate’s Chain of Trust”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product does not follow, or incorrectly follows, the chain of trust for a certificate back to a trusted root certificate.

How serious is CWE-296?

MITRE rates the likelihood of exploit as Low. It can affect non-repudiation, integrity, confidentiality, availability, with impacts such as hide activities, gain privileges or assume identity, execute unauthorized code or commands. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-296?

Ensure that proper certificate checking is included in the system design. Understand, and properly implement all checks necessary to ensure the integrity of certificate trust integrity.

Can Codefreex check my site for CWE-296?

Yes. A senior engineer reviews your site, store or app for CWE-296 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.

Which technologies does CWE-296 affect?

MITRE lists it as applicable to Web Based. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-296 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.