Use of a Broken or Risky Cryptographic Algorithm

Property	Value
Language	java
Severity
CWE	CWE-327: Use of a Broken or Risky Cryptographic Algorithm
OWASP	A03:2017 - Sensitive Data Exposure
Confidence Level	Low
Impact Level	Low
Likelihood Level	Low

Description

Implementing your own cryptographic message digest (hash) algorithms is risky because it's easy to introduce subtle flaws that weaken security. Instead, always use well-tested, standard library implementations like SHA-256.

Impact

If a custom message digest contains mistakes, attackers could break the hash, forge data, or access sensitive information. This can lead to data breaches, loss of integrity, and compromise of authentication or encryption features in your application.