Difference between revisions of "Using a broken or risky cryptographic algorithm"

From OWASP
Jump to: navigation, search
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
+
{{Template:Vulnerability}}
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
  
==Overview==
+
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
The use of a broken or risky cryptographic algorithm is an unnecessary risk that may result in the disclosure of sensitive information.
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
  
==Consequences ==
+
==Description==
 +
Attempting to create non-standard and non-tested algorithms, using weak algorithms, or applying algorithms incorrectly will pose a high weakness to data that is meant to be secure.
  
* Confidentiality: The confidentiality of sensitive data may be compromised by the use of a broken or risky cryptographic algorithm.
+
'''Consequences'''
  
* Integrity: The integrity of sensitive data may be compromised by the use of a broken or risky cryptographic algorithm.
+
* Confidentiality: The confidentiality of sensitive data may be compromised by the use of a broken or risky cryptographic algorithm.
 +
* Integrity: The integrity of sensitive data may be compromised by the use of a broken or risky cryptographic algorithm.
 +
* Accountability: Any accountability to message content preserved by cryptography may be subject to attack.
  
* Accountability: Any accountability to message content preserved by cryptography may be subject to attack.
+
'''Exposure period'''
  
==Exposure period ==
+
* Design: The decision as to what cryptographic algorithm to utilize is generally made at design time.
  
* Design: The decision as to what cryptographic algorithm to utilize is generally made at design time.
+
'''Platform'''
  
==Platform ==
+
* Languages: All
 +
* Operating platforms: All
  
* Languages: All
+
'''Required resources'''
 
+
* Operating platforms: All
+
 
+
==Required resources ==
+
  
 
Any
 
Any
  
==Severity ==
+
'''Severity'''
  
 
High
 
High
  
==Likelihood   of exploit ==
+
'''Likelihood of exploit'''
  
 
Medium to High
 
Medium to High
  
==Avoidance and mitigation ==
+
Since the state of cryptography advances so rapidly, it is common to find algorithms, which previously were considered to be safe, currently considered unsafe. In some cases, things are discovered, or processing speed increases to the degree that the cryptographic algorithm provides little more benefit than the use of no cryptography at all.
  
* Design: Use a cryptographic algorithm that is currently considered to be strong by experts in the field.
+
==Risk Factors==
  
==Discussion ==
+
* Use of custom cryptographic algorithms.
 +
* Use of weak and/or untested public algorithms.
  
Since the state of cryptography advances so rapidly, it is common to find algorithms, which previously were considered to be safe, currently considered unsafe. In some cases, things are discovered, or processing speed increases to the degree that the cryptographic algorithm provides little more benefit than the use of no cryptography at all.
+
==Examples==
 
+
==Examples ==
+
  
 
In C/C++:
 
In C/C++:
Line 57: Line 56:
 
Cipher des=Cipher.getInstance("DES...);
 
Cipher des=Cipher.getInstance("DES...);
 
des.initEncrypt(key2);
 
des.initEncrypt(key2);
<pre>
+
</pre>
  
==Related problems ==
 
  
* [[Failure to encrypt data]]
+
==Related [[Attacks]]==
  
==Categories ==
+
* [[Attack 1]]
 +
* [[Attack 2]]
  
[[Category:Vulnerability]]
 
  
[[Category:Protocol Errors]]</pre>
+
==Related [[Vulnerabilities]]==
 +
 
 +
* [[Failure to encrypt data]]
 +
 
 +
 
 +
 
 +
==Related [[Controls]]==
 +
 
 +
* Design: Use a cryptographic algorithm that is currently considered to be strong by experts in the field.
 +
 
 +
 
 +
==Related [[Technical Impacts]]==
 +
 
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 
 +
 
 +
==References==
 +
 
 +
TBD
 +
 
 +
 
 +
__NOTOC__
 +
 
 +
 
 +
[[Category:OWASP ASDR Project]]
 +
[[Category:Vulnerability]]
 +
[[Category:Cryptographic Vulnerability]]

Latest revision as of 21:05, 20 February 2009

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



Last revision (mm/dd/yy): 02/20/2009

Vulnerabilities Table of Contents

Description

Attempting to create non-standard and non-tested algorithms, using weak algorithms, or applying algorithms incorrectly will pose a high weakness to data that is meant to be secure.

Consequences

  • Confidentiality: The confidentiality of sensitive data may be compromised by the use of a broken or risky cryptographic algorithm.
  • Integrity: The integrity of sensitive data may be compromised by the use of a broken or risky cryptographic algorithm.
  • Accountability: Any accountability to message content preserved by cryptography may be subject to attack.

Exposure period

  • Design: The decision as to what cryptographic algorithm to utilize is generally made at design time.

Platform

  • Languages: All
  • Operating platforms: All

Required resources

Any

Severity

High

Likelihood of exploit

Medium to High

Since the state of cryptography advances so rapidly, it is common to find algorithms, which previously were considered to be safe, currently considered unsafe. In some cases, things are discovered, or processing speed increases to the degree that the cryptographic algorithm provides little more benefit than the use of no cryptography at all.

Risk Factors

  • Use of custom cryptographic algorithms.
  • Use of weak and/or untested public algorithms.

Examples

In C/C++:

EVP_des_ecb();

In Java:

Cipher des=Cipher.getInstance("DES...);
des.initEncrypt(key2);


Related Attacks


Related Vulnerabilities


Related Controls

  • Design: Use a cryptographic algorithm that is currently considered to be strong by experts in the field.


Related Technical Impacts


References

TBD