This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Using a broken or risky cryptographic algorithm"
(→Risk Factors) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Template:Vulnerability}} | {{Template:Vulnerability}} | ||
{{Template:SecureSoftware}} | {{Template:SecureSoftware}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| − | [[ | + | [[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]] |
| − | |||
==Description== | ==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. | 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. | ||
Latest revision as of 02:05, 21 February 2009
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
Last revision (mm/dd/yy): 02/21/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
