Race condition in checking for certificate revocation
#REDIRECT Race Conditions
Last revision (mm/dd/yy): 04/7/2009
If the revocation status of a certificate is not checked before each privilege requiring action, the system may be subject to a race condition, in which their certificate may be used before it is checked for revocation.
- Authentication: Trust may be assigned to an entity who is not who it claims to be.
- Integrity: Data from an untrusted (and possibly malicious) source may be integrated.
- Confidentiality: Date may be disclosed to an entity impersonating a trusted entity, resulting in information disclosure.
- Design: Checks for certificate revocation should be included in the design of a system
- Design: One can choose to use a language which abstracts out this part of the authentication process.
- Languages: Languages which do not abstract out this part of the process.
- Operating platforms: All
Minor trust: Users must attempt to interact with the malicious system.
Likelihood of exploit
If a certificate is revoked after the initial check, all subsequent actions taken with the owner of the revoked certificate will loose all benefits guaranteed by the certificate. In fact, it is almost certain that the use of a revoked certificate indicates malicious activity.
If the certificate is checked before each access of a protected resource, the delay subject to a possible race condition becomes almost negligible and significantly reduces the risk associated with this issue.
if (!(cert = SSL_get_peer(certificate(ssl)) || !host) foo=SSL_get_veryify_result(ssl); if (X509_V_OK==foo) //do stuff foo=SSL_get_veryify_result(ssl); //do more stuff without the check.
- Failure to follow chain of trust in certificate validation
- Failure to validate host-specific certificate data
- Failure to validate certificate expiration
- Failure to check for certificate revocation
- Design: Ensure that certificates are checked for revoked status before each use of a protected resource
Related Technical Impacts