This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Using a broken or risky cryptographic algorithm

Revision as of 18:50, 13 December 2008 by Kcfredman (talk | contribs) (Risk Factors)

Jump to: navigation, search

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

ASDR Table of Contents

Last revision (mm/dd/yy): 12/13/2008


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


  • Languages: All
  • Operating platforms: All

Required resources




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.


In C/C++:


In Java:

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

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