CVE-2024-5617
Received Received - Intake

Account Lock Bypass in User Store Integration

Vulnerability report for CVE-2024-5617, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: WSO2 LLC

Description

The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account. This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-02
Last Modified
2026-11-02
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-799 The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a flaw in the account lockout mechanism where identical usernames in primary and secondary user stores cause the lock condition to only apply to the secondary account. This allows attackers to bypass the lockout and perform brute force attacks against the primary account.

Detection Guidance

This vulnerability allows brute force attacks due to improper account lockout enforcement. To detect it, monitor authentication logs for repeated failed login attempts against accounts, especially where identical usernames exist in multiple user stores. Check for patterns of continuous login attempts without account lockouts being triggered.

Impact Analysis

An attacker could exploit this to repeatedly guess passwords for the primary account, potentially gaining unauthorized access to sensitive data or systems. This could lead to data breaches, account takeovers, or other security incidents.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, which may violate GDPR's data protection requirements and HIPAA's safeguards for protected health information. The lack of proper account lockout enforcement increases the risk of data breaches, potentially resulting in non-compliance with these regulations.

Mitigation Strategies

Review and update account lockout policies to ensure they apply consistently across all user stores. Verify that identical usernames in primary and secondary stores are handled uniformly to prevent bypass of lockout mechanisms.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2024-5617. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...