CWE-307: Improper Restriction of Excessive Authentication Attempts

BaseDraft

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

View on MITRE
Back to CWE Lookup

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-307 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-307, Improper Restriction of Excessive Authentication Attempts, 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

Apply Libraries or Frameworks controls for Improper Restriction of Excessive Authentication Attempts

MITRE associates mitigation with Architecture and Design; the listed strategies include Libraries or Frameworks; documented detection approaches include Dynamic Analysis with Automated Results Interpretation, Dynamic Analysis with Manual Results Interpretation, Manual Static Analysis - Source Code, and Automated Static Analysis - Source Code. Use these source-defined anchors to turn CWE-307 into implementation, review, and verification checks for the affected component.

CWE-307: Improper Restriction of Excessive Authentication AttemptsMITRE CWE

Triage CWE-307 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-307, Improper Restriction of Excessive Authentication Attempts, 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-307

Apply MITRE's full root-cause mapping guidance when using CWE-307, Improper Restriction of Excessive Authentication Attempts. 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-307 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-307, Improper Restriction of Excessive Authentication Attempts. 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-307: Improper Restriction of Excessive Authentication Attempts?+

CWE-307: Improper Restriction of Excessive Authentication Attempts is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

What are the security consequences of Improper Restriction of Excessive Authentication Attempts?+

If exploited, CWE-307 (Improper Restriction of Excessive Authentication Attempts) it can compromise Access Control, leading to outcomes such as Bypass Protection Mechanism.

How do you prevent or mitigate Improper Restriction of Excessive Authentication Attempts?+

Recommended mitigations for CWE-307 include: Common protection mechanisms include: Disconnecting the user after a small number of failed attempts Implementing a timeout Locking out a targeted account Requiring a computational task on the user's part.

How is Improper Restriction of Excessive Authentication Attempts detected?+

CWE-307 can be detected using Dynamic Analysis with Automated Results Interpretation, Dynamic Analysis with Manual Results Interpretation, Manual Static Analysis - Source Code, Automated Static Analysis - Source Code, Automated Static Analysis and Architecture or Design Review. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Improper Restriction of Excessive Authentication Attempts?+

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

What are real-world examples of Improper Restriction of Excessive Authentication Attempts?+

MITRE documents real CVEs mapped to CWE-307, including CVE-2019-0039, CVE-1999-1152, CVE-2001-1291, CVE-2001-0395 and CVE-2001-1339. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

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

A CWE (Common Weakness Enumeration) like CWE-307 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