Live › vulnerability › CVE-2024-5617
When the same username exists in both a primary and a secondary user store, the account lock only applies to the secondary account. An attacker can keep guessing passwords against the primary account without being locked out.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 06:21 UTC. All times on this page are UTC.
Systems that authenticate users against a primary user store and a secondary user store where identical usernames exist in both, with account lockout enabled. Deployments with a single user store or unique usernames across stores are not described as affected. The sources do not name the product or versions.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2024-5617")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.