Skip to content
StrikeOps

No Rate Limiting or Lockout on Login

MediumTypical severity Web applications and APIsCWE-307ATT&CK T1110

01Description

The application's authentication endpoint did not limit the number or rate of failed login attempts.

02Impact

Attackers can perform unlimited password guessing, password spraying and credential stuffing against user accounts, which is likely to succeed against users with weak or reused passwords.

03Severity

Typically

Medium

Typically Medium. Medium by default. High where MFA is not enforced and the application is internet-facing with many users.

04How to verify

  1. 1Submit a controlled series of failed logins against a dedicated test account and observe whether requests are slowed, challenged or blocked.
  2. 2Check whether limits apply per account, per source IP or both.
  3. 3Check whether MFA would stop a guessed password from being usable.

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. 1Apply rate limiting per account and per source, with progressive delays or temporary lockout.
  2. 2Add bot protection or CAPTCHA after repeated failures.
  3. 3Enforce MFA and screen passwords against breached-password lists.
  4. 4Alert on spikes in failed logins.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo