Home / Vulnerability Database / Groovy : Hardcoded salt
Groovy

Groovy : Hardcoded salt

Overview

One of the attack methods on a password authentication system uses tables of pre-computed hash values of popular passwords. Salt is an arbitrary string, which is fed into the hash function concatenated with the original data (usually a password) in order to prevent such an attack.

Constant salt hardcoded in the application’s source code may jeopardize the security of the system. At least, the value of the salt is accessible to all the application developers. If the same salt value is used in the final version of the application, it will be possible to remove it only through an update.

Since constant string values are easily extracted from the application by a decompiler, an attacker can gain access to salt value even without an access to the source code of the application.

Sensitive Data Exposure vulnerabilities take the third place in the “OWASP Top 10 2017” web-application vulnerabilities ranking.

MEDIUM

DerScanner Severity Score

Do you want to fix Groovy : Hardcoded salt in your application?

See also

Groovy

Groovy : Weak hashing algorithm

Groovy

Groovy : Unsafe padding

Groovy

Groovy : Null encryption key