Difference between revisions of "Using a key past its expiration date"
(Reverting to last version not containing links to s1.shard.jp)
(Reverting to last version not containing links to www.textlitaroze.com)
|Line 1:||Line 1:|
Latest revision as of 13:29, 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 use of a cryptographic key or password past its expiration date diminishes its safety significantly.
Authentication: The cryptographic key in question may be compromised, providing a malicious user with a method for authenticating as the victim.
- Design: The handling of key expiration should be considered during the design phase - largely pertaining to user interface design.
- Run time: Users are largely responsible for the use of old keys.
- Languages: All
- Platforms: All
Likelihood of exploit
While the expiration of keys does not necessarily ensure that they are compromised, it is a significant concern that keys which remain in use for prolonged periods of time have a decreasing probability of integrity.
For this reason, it is important to replace keys within a period of time proportional to their strength.
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
- Design: Adequate consideration should be put in to the user interface in order to notify users prior to the key's expiration, to explain the importance of new key generation, and to walk users through the process as painlessly as possible.
- Run time: Users must heed warnings and generate new keys and passwords when they expire.
Related Technical Impacts