CWE-299: Improper Check for Certificate Revocation

Description

The product does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised.

Extended Description

An improper check for certificate revocation is a far more serious flaw than related certificate failures. This is because the use of any revoked certificate is almost certainly malicious. The most common reason for certificate revocation is compromise of the system in question, with the result that no legitimate servers will be using a revoked certificate, unless they are sorely out of sync.

ThreatScore

Threat Mapped score: 0.0

Industry: Finiancial

Threat priority: Unclassified

Observed Examples (CVEs)

CVE: CVE-2011-2014

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

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

Antivirus product does not check whether certificates from signed executables have been revoked.
CVE: CVE-2009-3046

Web browser does not check if any intermediate certificates are revoked.
CVE: CVE-2009-0161

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

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

Router can permanently cache certain public keys, which would allow bypass if the certificate is later revoked.
CVE: CVE-2009-1358

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

chain: language interpreter does not properly check the return value from an OSCP function, allowing bypass using a revoked certificate.
CVE: CVE-2008-4679

chain: web service component does not call the expected method, which prevents a check for revoked certificates.
CVE: CVE-2006-4410

Certificate revocation list not searched for certain certificates.
CVE: CVE-2006-4409

Product cannot access certificate revocation list when an HTTP proxy is being used.

Related Attack Patterns (CAPEC)

N/A

Attack TTPs

N/A

Modes of Introduction

Phase	Note
Implementation	When the product uses certificate pinning, the developer might not properly validate all relevant components of the certificate before pinning the certificate. This can make it difficult or expensive to test after the pinning is complete.
Implementation	REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Common Consequences

Impact: Gain Privileges or Assume Identity — Notes: Trust may be assigned to an entity who is not who it claims to be.
Impact: Other — Notes: Data from an untrusted (and possibly malicious) source may be integrated.
Impact: Read Application Data — Notes: Data may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.

Potential Mitigations

Architecture and Design: Ensure that certificates are checked for revoked status. (N/A)
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. (N/A)

Applicable Platforms

None (Not Language-Specific, Undetermined)

Demonstrative Examples

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

Body: Because this code does not use SSL_get_verify_results() to check the certificate, it could accept certificates that have been revoked (X509_V_ERR_CERT_REVOKED). The product could be communicating with a malicious host.

if (cert = SSL_get_peer_certificate(ssl)) { // got a certificate, do secret things

Notes

No notes available.

← Back to CWE list