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

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
 +
{{Template:Vulnerability}}
  
==Overview==
+
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
  
The use of a cryptographic key or password past its expiration date diminishes its safety significantly.
 
  
==Consequences ==
+
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
* Authentication: The cryptographic key in question may be compromised, providing a malicious user with a method for authenticating as the victim.
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
  
==Exposure period ==
+
[[ASDR Table of Contents]]
 +
__TOC__
  
* 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.
+
==Description==
  
==Platform ==
+
The use of a cryptographic key or password past its expiration date diminishes its safety significantly.
  
* Languages: All
+
'''Consequences'''
  
* Platforms: All
+
Authentication: The cryptographic key in question may be compromised, providing a malicious user with a method for authenticating as the victim.
  
==Required resources ==
+
'''Exposure period'''
  
Any
+
* 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.
  
==Severity ==
+
'''Platform'''
  
Low
+
* Languages: All
 +
* Platforms: All
  
==Likelihood  of exploit ==
+
'''Required resources'''
  
Low
+
Any
  
==Avoidance and mitigation ==
+
'''Severity'''
  
* 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.
+
Low
  
* Run time: Users must heed warnings and generate new keys and passwords when they expire.
+
'''Likelihood of exploit'''
  
==Discussion ==
+
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.  
 
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.  
Line 45: Line 47:
 
For this reason, it is important to replace keys within a period of time proportional to their strength.
 
For this reason, it is important to replace keys within a period of time proportional to their strength.
  
==Examples ==
+
 
 +
==Risk Factors==
 +
 
 +
TBD
 +
 
 +
==Examples==
  
 
In C/C++:
 
In C/C++:
Line 56: Line 63:
 
</pre>
 
</pre>
  
==Related problems ==
 
  
* [[Failure to check for certificate expiration]]
+
==Related [[Attacks]]==
  
 +
* [[Attack 1]]
 +
* [[Attack 2]]
  
[[Category:Vulnerability]]
 
  
[[Category:Cryptographic Vulnerability]]
+
==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 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.
 +
* 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]]
 
[[Category:OWASP_CLASP_Project]]

Revision as of 09:23, 3 October 2008

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


Last revision (mm/dd/yy): 10/3/2008

Vulnerabilities Table of Contents

ASDR Table of Contents

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 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.
  • Run time: Users must heed warnings and generate new keys and passwords when they expire.


Related Technical Impacts


References

TBD