Difference between revisions of "Testing for Weak or unenforced username policy (OTG-IDENT-005)"

From OWASP
Jump to: navigation, search
m (Andrew Muller moved page Testing for Weak or unenforced username policy (OWASP-AT-009) to Testing for Weak or unenforced username policy (OTG-IDENT-005): Align with common number and cross-product correlation initiative)
Line 1: Line 1:
{{Template:OWASP Testing Guide v4}}
+
== Summary ==
 +
 
 +
User account names are often highly structured (e.g. Joe Bloggs account name is jbloggs and Fred Nurks account name is fnurks) and valid account names can easily be guessed.
 +
 
 +
== Test objectives ==
 +
 
 +
Determine whether consistent account name structure renders the application vulnerable to account enumeration
 +
 
 +
Determine whether application's error messages permit account enumeration
 +
 
 +
== How to test ==
 +
 
 +
Determine the structure of account names
 +
 
 +
Evaluate the application's response to valid and invalid account names
 +
 
 +
Use different responses to valid and invalid account names to enumerate valid account names
 +
 
 +
Use account name dictionaries to enumerate valid account names
 +
 
 +
=== Example ===
 +
 
 +
<insert some images of account enumeration>
 +
 
 +
== Tools ==
  
  
== Brief Summary ==
 
<br>
 
..here: we describe in "natural language" what we want to test.
 
<br>
 
== Description of the Issue ==
 
<br>
 
...here: Short Description of the Issue: Topic and Explanation
 
<br>
 
== Black Box testing and example ==
 
'''Testing for Topic X vulnerabilities:''' <br>
 
...<br>
 
'''Result Expected:'''<br>
 
...<br><br>
 
 
== References ==
 
== References ==
'''Whitepapers'''<br>
+
 
...<br>
+
 
'''Tools'''<br>
+
== Remediation ==
...<br>
+
 
 +
Ensure the application returns consistent generic error messages in response to invalid account name, password or other user credentials entered during the login process.

Revision as of 09:31, 5 November 2013

Summary

User account names are often highly structured (e.g. Joe Bloggs account name is jbloggs and Fred Nurks account name is fnurks) and valid account names can easily be guessed.

Test objectives

Determine whether consistent account name structure renders the application vulnerable to account enumeration

Determine whether application's error messages permit account enumeration

How to test

Determine the structure of account names

Evaluate the application's response to valid and invalid account names

Use different responses to valid and invalid account names to enumerate valid account names

Use account name dictionaries to enumerate valid account names

Example

<insert some images of account enumeration>

Tools

References

Remediation

Ensure the application returns consistent generic error messages in response to invalid account name, password or other user credentials entered during the login process.