Home / Vulnerability Database / PL or SQL : Unsafe password management
PL/SQL
PL or SQL : Unsafe password management
Classification
OWASP Top 10 2017
OWASP Top 10 2021
OWASP ASVS
Overview
Unsecure work with passwords.
Passwords must be stored in the database in an encrypted form. The use of passwords in an unencrypted form is unsafe. In particular, if an application uses a password stored in plaintext in a configuration file, this can lead to the application data being compromised.
Developers often believe that the data stored in the configuration file is securely protected. This assumption simplifies the attacker’s job. Good password management guidelines require that a password never be stored in plaintext.
Set secure values for password policy settings. Limit the number of authorization attempts, the session length, control the password characters number and the password complexity.
References
- OWASP Top 10 2013-A5-Security Misconfiguration
- OWASP Top 10 2013-A6-Sensitive Data Exposure
- owa_sec - docs.oracle.com
- OWASP Top 10 2017 A2-Broken Authentication
- OWASP Top 10 2017-A3-Sensitive Data Exposure
- CWE-261: Weak Encoding for Password
- CWE CATEGORY: OWASP Top Ten 2017 Category A2 - Broken Authentication
- CWE CATEGORY: OWASP Top Ten 2017 Category A6 - Security Misconfiguration
LOW
DerScanner Severity Score
Do you want to fix PL or SQL : Unsafe password management in your application?
See also
PL/SQL
PL or SQL : Open redirect
PL/SQL
PL or SQL : Cross-site scripting (XSS)
PL/SQL
