Account lock bypass in WSO2 products enables brute force attacks
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
WSO2 API Manager, WSO2 Identity Server, WSO2 Carbon Identity Management and WSO2 Carbon User Manager Kernel fail to enforce account locks on the primary user store when identical usernames exist in a secondary user store. The lock applies only to the secondary account, so the primary account keeps accepting login attempts. A remote attacker without credentials can make repeated password guesses against the primary account and potentially gain unauthorized access (CWE-799).
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| WSO2 | WSO2 API Manager | 4.0.0 to before 4.0.0.298; 4.2.0 to before 4.2.0.95; 4.3.0 to before 4.3.0.13 | 4.0.0.298, 4.2.0.95, 4.3.0.13 | Patch available | CNA |
| WSO2 | WSO2 Identity Server | 5.11.0 to before 5.11.0.348; 6.0.0 to before 6.0.0.194; 6.1.0 to before 6.1.0.162; 7.0.0 to before 7.0.0.33 | 5.11.0.348, 6.0.0.194, 6.1.0.162, 7.0.0.33 | Patch available | CNA |
| WSO2 | WSO2 Carbon Identity Management | 5.18.187 to before 5.18.187.259; 5.23.8 to before 5.23.8.180; 5.24.8 to before 5.24.8.5; 5.25.92 to before 5.25.92.84; 5.25.705 to before 5.25.705.5; 7.0.78 to before 7.0.78.19 | 5.18.187.259, 5.23.8.180, 5.24.8.5, 5.25.92.84, 5.25.705.5, 7.0.78.19 | Patch available | CNA |
| WSO2 | WSO2 Carbon User Manager Kernel | 4.6.1 to before 4.6.1.114; 4.7.1 to before 4.7.1.53; 4.8.1 to before 4.8.1.16; 4.9.0 to before 4.9.0.58; 4.9.26 to before 4.9.26.7; 4.10.9 to before 4.10.9.17 | 4.6.1.114, 4.7.1.53, 4.8.1.16, 4.9.0.58, 4.9.26.7, 4.10.9.17 | Patch available | CNA |
- WSO2 API Manager VendorWSO2 Affected 4.0.0 to before 4.0.0.298; 4.2.0 to before 4.2.0.95; 4.3.0 to before 4.3.0.13 Fixed in 4.0.0.298, 4.2.0.95, 4.3.0.13 Patch available CNA
- WSO2 Identity Server VendorWSO2 Affected 5.11.0 to before 5.11.0.348; 6.0.0 to before 6.0.0.194; 6.1.0 to before 6.1.0.162; 7.0.0 to before 7.0.0.33 Fixed in 5.11.0.348, 6.0.0.194, 6.1.0.162, 7.0.0.33 Patch available CNA
- WSO2 Carbon Identity Management VendorWSO2 Affected 5.18.187 to before 5.18.187.259; 5.23.8 to before 5.23.8.180; 5.24.8 to before 5.24.8.5; 5.25.92 to before 5.25.92.84; 5.25.705 to before 5.25.705.5; 7.0.78 to before 7.0.78.19 Fixed in 5.18.187.259, 5.23.8.180, 5.24.8.5, 5.25.92.84, 5.25.705.5, 7.0.78.19 Patch available CNA
- WSO2 Carbon User Manager Kernel VendorWSO2 Affected 4.6.1 to before 4.6.1.114; 4.7.1 to before 4.7.1.53; 4.8.1 to before 4.8.1.16; 4.9.0 to before 4.9.0.58; 4.9.26 to before 4.9.26.7; 4.10.9 to before 4.10.9.17 Fixed in 4.6.1.114, 4.7.1.53, 4.8.1.16, 4.9.0.58, 4.9.26.7, 4.10.9.17 Patch available CNA
Remediation
Upgrade WSO2 API Manager to 4.0.0.298, 4.2.0.95 or 4.3.0.13. Upgrade WSO2 Identity Server to 5.11.0.348, 6.0.0.194, 6.1.0.162 or 7.0.0.33. Upgrade WSO2 Carbon Identity Management to 5.18.187.259, 5.23.8.180, 5.24.8.5, 5.25.92.84, 5.25.705.5 or 7.0.78.19. Upgrade WSO2 Carbon User Manager Kernel to 4.6.1.114, 4.7.1.53, 4.8.1.16, 4.9.0.58, 4.9.26.7 or 4.10.9.17.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
- Fix · CNA WSO2 API Manager (WSO2) Fixed in 4.0.0.298, 4.2.0.95, 4.3.0.13
- Fix · CNA WSO2 Identity Server (WSO2) Fixed in 5.11.0.348, 6.0.0.194, 6.1.0.162, 7.0.0.33
- Fix · CNA WSO2 Carbon Identity Management (WSO2) Fixed in 5.18.187.259, 5.23.8.180, 5.24.8.5, 5.25.92.84, 5.25.705.5, 7.0.78.19
- Fix · CNA WSO2 Carbon User Manager Kernel (WSO2) Fixed in 4.6.1.114, 4.7.1.53, 4.8.1.16, 4.9.0.58, 4.9.26.7, 4.10.9.17
Timeline
- 2026-11-02 Threatist record created from CVE-2024-5617
- 2026-11-02 Alias added: GHSA-wxh9-84jx-g888
- 2026-11-02 CISA SSVC decision points changed
References
More WSO2 vulnerabilities
- TI-2026-04755 Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account Takeover KEVCVSS 3.1CRITICAL 10.0
- TI-2022-11928 Certain WSO2 products allow unrestricted file upload with resultant remote code execution. KEVCVSS 3.1CRITICAL 9.8
- TI-2022-18808 An issue was discovered in WSO2 Enterprise Integrator 6.4.0. CVSS 3.1MEDIUM 6.1
- TI-2020-15069 The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0… CVSS 3.1CRITICAL 9.1
- TI-2023-15163 A reflected cross-site scripting (XSS) vulnerability in /authenticationendpoint/login.do… CVSS 3.1MEDIUM 6.1
- TI-2022-04130 WSO2 carbon-registry Advanced Search advancedSearchForm-ajaxprocessor.jsp cross site scripting CVSS 3.1MEDIUM 6.1
Sources
- CVE-2024-5617 · CVE Program
- CVE-2024-5617 · NVD
- FIRST EPSS
- GHSA-wxh9-84jx-g888 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences