Medium (4.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
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.
Severity
CVSS 3.1
4.8 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2%(unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
Show the promptExplain CVE-2024-5617 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-5617?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-5617?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-5617 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.