CWE-299 Base Draft Medium likelihood

Improper Check for Certificate Revocation

This vulnerability occurs when an application fails to properly verify whether a security certificate has been revoked, potentially allowing it to accept and use a compromised or untrustworthy…

Definition

What is CWE-299?

This vulnerability occurs when an application fails to properly verify whether a security certificate has been revoked, potentially allowing it to accept and use a compromised or untrustworthy certificate.
Failing to check certificate revocation is a critical security gap, more severe than other certificate errors. When a certificate is revoked, it's almost always because the associated private key has been exposed or the issuing authority no longer trusts it—meaning any system still using that certificate is likely compromised. Legitimate services should never operate with a revoked certificate unless they have a serious configuration or synchronization problem. For developers, this means your application could mistakenly trust a malicious actor impersonating a legitimate server. To prevent this, always implement and test proper revocation checking mechanisms like CRL (Certificate Revocation List) or OCSP (Online Certificate Status Protocol) in your TLS/SSL handshake logic, and ensure these checks cannot be bypassed by network errors or performance shortcuts.
Auswirkungen in der Praxis

Real-world CVEs caused by CWE-299

  • CVE-2011-2014

    LDAP-over-SSL implementation does not check Certificate Revocation List (CRL), allowing spoofing using a revoked certificate.

  • CVE-2011-0199

    Operating system does not check Certificate Revocation List (CRL) in some cases, allowing spoofing using a revoked certificate.

  • CVE-2010-5185

    Antivirus product does not check whether certificates from signed executables have been revoked.

  • CVE-2009-3046

    Web browser does not check if any intermediate certificates are revoked.

  • CVE-2009-0161

    chain: Ruby module for OCSP misinterprets a response, preventing detection of a revoked certificate.

  • CVE-2011-2701

    chain: incorrect parsing of replies from OCSP responders allows bypass using a revoked certificate.

  • CVE-2011-0935

    Router can permanently cache certain public keys, which would allow bypass if the certificate is later revoked.

  • CVE-2009-1358

    chain: OS package manager does not properly check the return value, allowing bypass using a revoked certificate.

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

  1. 1

    Identifiziere einen Codepfad, der nicht vertrauenswürdige Eingaben ohne Validierung verarbeitet.

  2. 2

    Erzeuge eine Payload, die das unsichere Verhalten auslöst — Injection, Traversal, Overflow oder Logik-Missbrauch.

  3. 3

    Liefere die Payload über einen normalen Request aus und beobachte die Reaktion der Anwendung.

  4. 4

    Iteriere, bis die Antwort Daten preisgibt, Angreifer-Code ausführt oder Berechtigungen eskaliert.

Verwundbares Codebeispiel

Vulnerable C

The following OpenSSL code ensures that there is a certificate before continuing execution.

Verwundbar C 
if (cert = SSL_get_peer_certificate(ssl)) {
```
// got a certificate, do secret things*
Sicheres Codebeispiel

Secure pseudo

Sicher pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Präventions-Checkliste

How to prevent CWE-299

  • Architecture and Design Ensure that certificates are checked for revoked status.
  • 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 revoked status.
Erkennungssignale

How to detect CWE-299

Automated Static Analysis High

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

Plexicus Auto-Fix

Plexicus erkennt CWE-299 automatisch und öffnet in unter 60 Sekunden einen Fix-PR.

Codex Remedium scannt jeden Commit, identifiziert genau diese Schwachstelle und liefert einen reviewer-ready Pull Request mit dem Patch. Keine Tickets. Keine Hand-offs.

Demo anfordern Plexicus kostenlos testen
Häufig gestellte Fragen

Frequently asked questions

Was ist CWE-299?

This vulnerability occurs when an application fails to properly verify whether a security certificate has been revoked, potentially allowing it to accept and use a compromised or untrustworthy certificate.

Wie gravierend ist CWE-299?

MITRE stuft die Exploit-Wahrscheinlichkeit als mittel ein — eine Ausnutzung ist realistisch, erfordert aber meist bestimmte Bedingungen.

Welche Sprachen oder Plattformen sind von CWE-299 betroffen?

MITRE hat für diese CWE keine betroffenen Plattformen spezifiziert — sie kann in den meisten Anwendungs-Stacks auftreten.

Wie kann ich CWE-299 verhindern?

Ensure that certificates are checked for revoked status. If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the revoked status.

Wie erkennt und behebt Plexicus CWE-299?

Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-299 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.

Wo erfahre ich mehr über CWE-299?

MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/299.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.

Verwandte Schwachstellen

Weaknesses related to CWE-299

CWE-295 Parent

Improper Certificate Validation

This vulnerability occurs when an application fails to properly verify the authenticity of a digital certificate, or performs the…

CWE-296 Sibling

Improper Following of a Certificate's Chain of Trust

This vulnerability occurs when software fails to properly validate the entire certificate chain back to a trusted root authority. This…

CWE-297 Sibling

Improper Validation of Certificate with Host Mismatch

This vulnerability occurs when an application accepts a valid SSL/TLS certificate without properly verifying that it actually belongs to…

CWE-298 Sibling

Improper Validation of Certificate Expiration

This vulnerability occurs when an application fails to properly check if a digital certificate has expired, potentially trusting…

CWE-599 Sibling

Missing Validation of OpenSSL Certificate

This vulnerability occurs when an application uses OpenSSL but fails to properly verify server certificates by not calling…

CWE-370 Child

Missing Check for Certificate Revocation after Initial Check

This vulnerability occurs when software only verifies a certificate's revocation status once, then continues to trust it for subsequent…

Ressourcen

Further reading

Bereit, wenn du es bist

Schluss mit dem Bezahlen pro Entwickler.
Schließ den Kreislauf.

Plexicus ist die KI-native ASPM, die scannt, filtert, fixt, pentestet und erklärt — autonom. Unbegrenzte Entwickler, unbegrenzte Repos, Fair-Use-KI-Aktionen. Echter kostenloser Tarif, €269/mo jährlich, wenn du bereit bist.

Kostenlos starten Demo buchen