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 "Password Plaintext Storage"
Weilin Zhong (talk | contribs) |
(→Risk Factors) (Tag: Visual edit) |
||
| (10 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Template:Vulnerability}} | ||
{{Template:Fortify}} | {{Template:Fortify}} | ||
| − | {{ | + | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' |
| + | |||
| + | [[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]] | ||
| − | == | + | ==Description== |
Storing a password in plaintext may result in a system compromise. | Storing a password in plaintext may result in a system compromise. | ||
| − | |||
| − | |||
Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. A programmer can attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password. | Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. A programmer can attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password. | ||
| Line 13: | Line 14: | ||
Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource. Developers sometimes believe that they cannot defend the application from someone who has access to the configuration, but this attitude makes an attacker's job easier. Good password management guidelines require that a password never be stored in plaintext. | Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource. Developers sometimes believe that they cannot defend the application from someone who has access to the configuration, but this attitude makes an attacker's job easier. Good password management guidelines require that a password never be stored in plaintext. | ||
| − | ==Examples == | + | |
| + | |||
| + | ==Risk Factors== | ||
| + | |||
| + | Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource. | ||
| + | |||
| + | |||
| + | ==Examples== | ||
The following code reads a password from a properties file and uses the password to connect to a database. | The following code reads a password from a properties file and uses the password to connect to a database. | ||
| Line 27: | Line 35: | ||
</pre> | </pre> | ||
| − | |||
| − | ==Related Attacks== | + | ==Related [[Attacks]]== |
| − | + | * [[Attack 1]] | |
| + | * [[Attack 2]] | ||
| − | |||
| − | [[ | + | ==Related [[Vulnerabilities]]== |
| − | + | * [[Vulnerability 1]] | |
| + | * [[Vulnerabiltiy 2]] | ||
| + | ==Related [[Controls]]== | ||
| + | |||
| + | * [[Password Management Countermeasure]] | ||
| + | |||
| + | |||
| + | ==Related [[Technical Impacts]]== | ||
| + | |||
| + | * [[Technical Impact 1]] | ||
| + | * [[Technical Impact 2]] | ||
| + | |||
| + | |||
| + | ==References== | ||
| + | |||
| + | TBD | ||
| + | |||
| + | [[Category:FIXME|add links | ||
| + | In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki> | ||
| + | |||
| + | Availability Vulnerability | ||
| + | Authorization Vulnerability | ||
| + | Authentication Vulnerability | ||
| + | Concurrency Vulnerability | ||
| + | Configuration Vulnerability | ||
| + | Cryptographic Vulnerability | ||
| + | Encoding Vulnerability | ||
| + | Error Handling Vulnerability | ||
| + | Input Validation Vulnerability | ||
| + | Logging and Auditing Vulnerability | ||
| + | Session Management Vulnerability]] | ||
| + | |||
| + | __NOTOC__ | ||
| + | |||
| + | [[Category:OWASP ASDR Project]] | ||
[[Category:Sensitive Data Protection Vulnerability]] | [[Category:Sensitive Data Protection Vulnerability]] | ||
| − | |||
[[Category:Java]] | [[Category:Java]] | ||
| − | |||
[[Category:Code Snippet]] | [[Category:Code Snippet]] | ||
| − | |||
[[Category:Password Management Vulnerability]] | [[Category:Password Management Vulnerability]] | ||
| + | [[Category:Vulnerability]] | ||
Latest revision as of 16:39, 19 May 2019
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Last revision (mm/dd/yy): 05/19/2019
Vulnerabilities Table of Contents
Description
Storing a password in plaintext may result in a system compromise.
Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. A programmer can attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password.
Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource. Developers sometimes believe that they cannot defend the application from someone who has access to the configuration, but this attitude makes an attacker's job easier. Good password management guidelines require that a password never be stored in plaintext.
Risk Factors
Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource.
Examples
The following code reads a password from a properties file and uses the password to connect to a database.
...
Properties prop = new Properties();
prop.load(new FileInputStream("config.properties"));
String password = prop.getProperty("password");
DriverManager.getConnection(url, usr, password);
...
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
TBD
