Skip to content
StrikeOps

Username Enumeration

LowTypical severity Web applications and APIsCWE-204

01Description

The application returned different responses, messages or response times for valid and invalid usernames on the login, registration or password reset functions.

02Impact

An attacker can build a list of valid accounts, which makes password spraying, credential stuffing and targeted phishing more effective.

03Severity

Typically

Low

Typically Low. Low on its own. Medium when combined with weak lockout or rate limiting, as valid usernames make password spraying far more effective.

04How to verify

  1. 1Submit valid and invalid usernames to login, registration and password reset functions.
  2. 2Compare response messages, status codes, lengths and timing.
  3. 3Record which functions reveal account existence.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Return identical messages and response behavior for valid and invalid accounts, such as 'If an account exists, you will receive an email'.
  2. 2Equalize response times where practical.
  3. 3Apply rate limiting to authentication endpoints.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo