Skip to content
OpenAdvisories

Weakness (CWE)

CWE-645: Overly Restrictive Account Lockout Mechanism

Base Incomplete

The product contains an account lockout protection mechanism, but the mechanism is too restrictive and can be triggered too easily, which allows attackers to deny service to legitimate users by causing their accounts to be locked out.

How to prevent it (3 mitigations)
  1. Architecture and Design

    Implement more intelligent password throttling mechanisms such as those that take IP address into account, in addition to the login name.

  2. Architecture and Design

    Implement a lockout timeout that grows as the number of incorrect login attempts goes up, eventually resulting in a complete lockout.

  3. Architecture and Design

    Consider alternatives to account lockout that would still be effective against password brute force attacks, such as presenting the user machine with a puzzle to solve (making it do some computation).

Source: MITRE CWE-645

9 results · Feed