Difference between revisions of "Failure to validate certificate expiration"
(Reverting to last version not containing links to www.textrodarb.com)
|(One intermediate revision by one other user not shown)|
Latest revision as of 13:30, 27 May 2009
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
Last revision (mm/dd/yy): 05/27/2009
The failure to validate certificate operation may result in trust being assigned to certificates which have been abandoned due to age.
- Integrity: The data read from the system vouched for by the expired certificate may be flawed due to malicious spoofing.
- Authentication: Trust afforded to the system in question - based on the expired certificate - may allow for spoofing attacks.
- Design: Certificate expiration handling should be performed in the design phase.
- Languages: All
- Platforms: All
Minor trust: Users must attempt to interact with the malicious system.
Likelihood of exploit
When the expiration of a certificate is not taken in to account, no trust has necessarily been conveyed through it; therefore, all benefit of certificate is lost.
if (!(cert = SSL_get_peer(certificate(ssl)) || !host) foo=SSL_get_veryify_result(ssl); if ((X509_V_OK==foo) || (X509_V_ERRCERT_NOT_YET_VALID==foo)) //do stuff
- Failure to follow chain of trust in certificate validation
- Failure to validate host-specific certificate data
- Key exchange without entity authentication
- Failure to check for certificate revocation
- Using a key past its expiration date
- Design: Check for expired certificates and provide the user with adequate information about the nature of the problem and how to proceed.
Related Technical Impacts