CVE-2024-5617
Last modified
CVE-2024-5617 is a medium-severity vulnerability rated 4.8/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| WSO2 | WSO2 API Manager | < 4.0.0; >= 4.0.0, < 4.0.0.298; >= 4.2.0, < 4.2.0.95; >= 4.3.0, < 4.3.0.13 |
| WSO2 | WSO2 Identity Server | < 5.11.0; >= 5.11.0, < 5.11.0.348; >= 6.0.0, < 6.0.0.194; >= 6.1.0, < 6.1.0.162; >= 7.0.0, < 7.0.0.33 |
| WSO2 | WSO2 Carbon Identity Management | >= 5.18.187, < 5.18.187.259; >= 5.23.8, < 5.23.8.180; >= 5.24.8, < 5.24.8.5; >= 5.25.92, < 5.25.92.84; >= 5.25.705, < 5.25.705.5; >= 7.0.78, < 7.0.78.19 |
| WSO2 | WSO2 Carbon User Manager Kernel | >= 4.6.1, < 4.6.1.114; >= 4.7.1, < 4.7.1.53; >= 4.8.1, < 4.8.1.16; >= 4.9.0, < 4.9.0.58; >= 4.9.26, < 4.9.26.7; >= 4.10.9, < 4.10.9.17 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2024-5617?
How severe is CVE-2024-5617?
How do I fix CVE-2024-5617?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-56157iTop is an web based IT Service Management tool. Prior to ve…6.3
- CVE-2024-56158XWiki is a generic wiki platform. It's possible to execute a…9.8
- CVE-2024-56159Astro is a web framework for content-driven websites. A bug …5.3
- CVE-2024-5616A Cross-Site Request Forgery (CSRF) vulnerability exists in …4.3
- CVE-2024-56161Improper signature verification in AMD CPU ROM microcode pat…7.2
- CVE-2024-56169A validation integrity issue was discovered in Fort through …5.3
- CVE-2024-56170A validation integrity issue was discovered in Fort through …5.3
- CVE-2024-56171libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-af…9.8
- CVE-2024-56173In Optimizely Configured Commerce before 5.2.2408, malicious…4.7
- CVE-2024-56174In Optimizely Configured Commerce before 5.2.2408, malicious…8.1
- CVE-2024-56175In Optimizely Configured Commerce before 5.2.2408, malicious…6.1
- CVE-2024-56178An issue was discovered in Couchbase Server 7.6.x through 7.…6.5
Are you affected by CVE-2024-5617?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
