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 "Empty String Password"
From OWASP
| Line 1: | Line 1: | ||
{{Template:Vulnerability}} | {{Template:Vulnerability}} | ||
{{Template:Fortify}} | {{Template:Fortify}} | ||
| − | |||
| − | |||
| − | |||
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| − | + | [[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]] | |
| − | [[ | ||
==Description== | ==Description== | ||
Revision as of 00:38, 21 February 2009
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): 02/21/2009
Vulnerabilities Table of Contents
Description
Using an empty string as a password is insecure.
It is never appropriate to use an empty string as a password. It is too easy to guess. Empty string password makes the authentication as weak as the user names, which are normally public or guessable. This make a brute-force attack against the login interface much easier.
Attackers try to obtain a log in account of the application.
Risk Factors
TBD
Examples
TBD
Related Attacks
- Brute force attack against application log in interface.
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
TBD
