CWE-295: Improper Certificate Validation | Causes and Fixes Skip to content

Security weakness

CWE-295 Improper Certificate Validation

A base-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-295?

Improper Certificate Validation: The product does not validate, or incorrectly validates, a certificate.

Business impact

What CWE-295 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.

  • Bypass Protection Mechanism
  • Gain Privileges or Assume Identity

Authentication

Sign-in that does not protect

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

  • Bypass Protection Mechanism
  • Gain Privileges or Assume Identity

Free security check

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

Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate.

Weakness ID
CWE-295
Type
Base
Status
Draft
Applies to
Go, Web Based, Mobile
Introduced during
Architecture and Design, Implementation

Prevention

How to fix CWE-295, phase by phase

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

  1. 01

    Architecture and Design

    • Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner’s public key.
  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 hostname.

Detection and evidence

How CWE-295 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 Analysis – Binary or BytecodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Bytecode Weakness Analysis – including disassembler + source code weakness analysis Binary Weakness Analysis – including disassembler + source code weakness analysis
  • Manual Static Analysis – Binary or BytecodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Binary / Bytecode disassembler – then use manual analysis for vulnerabilities & anomalies
  • Dynamic Analysis with Automated Results InterpretationAccording to SOAR [REF-1479], the following detection techniques may be useful: Web Application Scanner
  • Dynamic Analysis with Manual Results InterpretationAccording to SOAR [REF-1479], the following detection techniques may be useful: Man-in-the-middle attack tool
  • Manual Static Analysis – Source CodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Focused Manual Spotcheck – Focused manual analysis of source Manual Source Code Review (not inspections)

Real vulnerabilities it caused

  • CVE-2019-12496A Go framework for robotics, drones, and IoT devices skips verification of root CA certificates by default.
  • CVE-2014-1266Chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -> CWE-561 (Dead Code) ->.
  • CVE-2021-22909Chain: router’s firmware update procedure uses curl with "-k" (insecure) option that disables certificate validation (CWE-295), allowing adversary-in-the-middle (AITM) compromise with a malicious firmware image.
  • 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.

How we fix it

From finding to fixed: how Codefreex closes CWE-295

  1. 01

    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. 02

    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. 03

    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. 04

    Keep it fixed

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

FAQ

CWE-295: FAQs

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

What is CWE-295?

CWE-295, “Improper Certificate Validation”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product does not validate, or incorrectly validates, a certificate.

How serious is CWE-295?

It can affect integrity, authentication, with impacts such as bypass protection mechanism, gain privileges or assume identity. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-295?

Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner’s public key. If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.

Can Codefreex check my site for CWE-295?

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

MITRE lists it as applicable to Go, Web Based, Mobile. 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-295 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.