Read Time:2 Minute, 8 Second
Description
The software does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised.
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.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit: Medium
Related Weaknesses
CWE-295
CWE-404
Consequences
Access Control: Gain Privileges or Assume Identity
Trust may be assigned to an entity who is not who it claims to be.
Integrity, Other: Other
Data from an untrusted (and possibly malicious) source may be integrated.
Confidentiality: Read Application Data
Data may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.
Potential Mitigations
Phase: Architecture and Design
Description:
Ensure that certificates are checked for revoked status.
Phase: Implementation
Description:
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.
CVE References
- 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.
- CVE-2009-0642
- chain: language interpreter does not properly check the return value from an OSCP function, allowing bypass using a revoked certificate.
- CVE-2008-4679
- chain: web service component does not call the expected method, which prevents a check for revoked certificates.
- CVE-2006-4410
- Certificate revocation list not searched for certain certificates.
- CVE-2006-4409
- Product cannot access certificate revocation list when an HTTP proxy is being used.
