CWE-299: Improper Check for Certificate Revocation
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.
How it's found
Improper Check for Certificate Revocation is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
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.
Consequences
- Gain Privileges or Assume Identity: Trust may be assigned to an entity who is not who it claims to be.
- Other: Data from an untrusted (and possibly malicious) source may be integrated.
- Read Application Data: Data may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.
Mitigations
- 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.
Where this fits in a TurboPentest engagement
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Frequently asked questions
What is CWE-299?
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.
How do you find Improper Check for Certificate Revocation?
Improper Check for Certificate Revocation is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-299?
Gain Privileges or Assume Identity: Trust may be assigned to an entity who is not who it claims to be. Other: Data from an untrusted (and possibly malicious) source may be integrated. Read Application Data: Data may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.
Does TurboPentest test for Improper Check for Certificate Revocation?
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Related CWEs
Written and reviewed by
Michel Chamberland - Founder & CEO, IntegSec
CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security
Michel has spent 20+ years on offensive security teams including IBM X-Force Red and Trustwave SpiderLabs, leading penetration tests, red team engagements, and breach response for Fortune 500 customers. He is the founder of IntegSec and the architect of TurboPentest.
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a pentest