CWE-645: Overly Restrictive Account Lockout Mechanism

BaseIncompleteExploit Likelihood: High

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.

View on MITRE
Back to CWE Lookup

Extended Description

Account lockout is a security feature often present in applications as a countermeasure to the brute force attack on the password based authentication mechanism of the system. After a certain number of failed login attempts, the users' account may be disabled for a certain period of time or until it is unlocked by an administrator. Other security events may also possibly trigger account lockout. However, an attacker may use this very security feature to deny service to legitimate system users. It is therefore important to ensure that the account lockout security mechanism is not overly restrictive.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-645 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-645, Overly Restrictive Account Lockout Mechanism, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Address Overly Restrictive Account Lockout Mechanism during Architecture and Design

MITRE associates mitigation with Architecture and Design; recorded impacts include DoS: Resource Consumption (Other); the entry maps to CAPEC-2. Use these source-defined anchors to turn CWE-645 into implementation, review, and verification checks for the affected component.

CWE-645: Overly Restrictive Account Lockout MechanismMITRE CWE

Triage CWE-645 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-645, Overly Restrictive Account Lockout Mechanism, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-645

Apply MITRE's full root-cause mapping guidance when using CWE-645, Overly Restrictive Account Lockout Mechanism. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-645 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-645, Overly Restrictive Account Lockout Mechanism. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-645: Overly Restrictive Account Lockout Mechanism?+

CWE-645: Overly Restrictive Account Lockout Mechanism is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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. Account lockout is a security feature often present in applications as a countermeasure to the brute force attack on the password based authentication mechanism of the system. After a certain number of failed login attempts, the users' account may be disabled for a certain period of time or until it is unlocked by an administrator. Other security events may also possibly trigger account lockout. However, an attacker may use this very security feature to deny service to legitimate system users. It is therefore important to ensure that the account lockout security mechanism is not overly restrictive.

What are the security consequences of Overly Restrictive Account Lockout Mechanism?+

If exploited, CWE-645 (Overly Restrictive Account Lockout Mechanism) it can compromise Availability, leading to outcomes such as DoS: Resource Consumption (Other).

How do you prevent or mitigate Overly Restrictive Account Lockout Mechanism?+

Recommended mitigations for CWE-645 include: Implement more intelligent password throttling mechanisms such as those which take IP address into account, in addition to the login name. Implement a lockout timeout that grows as the number of incorrect login attempts goes up, eventually resulting in a complete lockout. 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 (makes it do some computation).

Which programming languages are affected by Overly Restrictive Account Lockout Mechanism?+

CWE-645 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-645 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement