Difference between revisions of "Using a key past its expiration date"

From OWASP
Jump to: navigation, search
(Reverting to last version not containing links to www.textlitaroze.com)
 
(12 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
+
{{Template:Vulnerability}}
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
  
==Overview==
+
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 +
 
 +
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
  
 +
==Description==
 
The use of a cryptographic key or password past its expiration date diminishes its safety significantly.
 
The use of a cryptographic key or password past its expiration date diminishes its safety significantly.
  
==Consequences ==
+
'''Consequences'''
  
* Authentication: The cryptographic key in question may be compromised, providing a malicious user with a method for authenticating as the victim.
+
Authentication: The cryptographic key in question may be compromised, providing a malicious user with a method for authenticating as the victim.
  
==Exposure period ==
+
'''Exposure period'''
  
* Design: The handling of key expiration should be considered during the design phase - largely pertaining to user interface design.
+
* 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.
  
* Run time: Users are largely responsible for the use of old keys.
+
'''Platform'''
  
==Platform ==
+
* Languages: All
 +
* Platforms: All
  
* Languages: All
+
'''Required resources'''
 
+
* Platforms: All
+
 
+
==Required resources ==
+
  
 
Any
 
Any
  
==Severity ==
+
'''Severity'''
  
 
Low
 
Low
  
==Likelihood   of exploit ==
+
'''Likelihood of exploit'''
  
 
Low
 
Low
  
==Avoidance and mitigation ==
+
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.
  
* Design: Adequate consideration should be put in to the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.
+
For this reason, it is important to replace keys within a period of time proportional to their strength.
  
* Run time: Users must heed warnings and generate new keys and passwords when they expire.
 
  
==Discussion ==
+
==Risk Factors==
  
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.
+
TBD
  
For this reason, it is important to replace keys within a period of time proportional to their strength.
+
==Examples==
 
+
==Examples ==
+
  
 
In C/C++:
 
In C/C++:
Line 57: Line 55:
 
</pre>
 
</pre>
  
==Related problems ==
 
  
* [[Failure to check for certificate expiration]]
+
==Related [[Attacks]]==
  
==Categories ==
+
* [[Attack 1]]
 +
* [[Attack 2]]
  
[[Category:Vulnerability]]
 
  
[[Category:Protocol Errors]]
+
==Related [[Vulnerabilities]]==
 +
 
 +
* [[Failure to check for certificate expiration]]
 +
 
 +
 
 +
==Related [[Controls]]==
 +
 
 +
* 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]]==
 +
 
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 
 +
 
 +
==References==
 +
 
 +
TBD
 +
 
 +
 
 +
__NOTOC__
 +
 
 +
 
 +
[[Category:OWASP ASDR Project]]
 +
[[Category:Vulnerability]]
 +
[[Category:Cryptographic Vulnerability]]
 +
[[Category:OWASP_CLASP_Project]]

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

Vulnerabilities Table of Contents

Description

The use of a cryptographic key or password past its expiration date diminishes its safety significantly.

Consequences

Authentication: The cryptographic key in question may be compromised, providing a malicious user with a method for authenticating as the victim.

Exposure period

  • 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.

Platform

  • Languages: All
  • Platforms: All

Required resources

Any

Severity

Low

Likelihood of exploit

Low

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.


Risk Factors

TBD

Examples

In C/C++:

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 


Related Attacks


Related Vulnerabilities


Related Controls

  • 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


References

TBD