Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in API Manager 4.0.0.298, API Manager 4.2.0.95, API Manager 4.3.0.13 and 16 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| WSO2 | API Manager | >=4.0.0 <4.0.0.298, >=4.2.0 <4.2.0.95, >=4.3.0 <4.3.0.13 | 4.0.0.298, 4.2.0.95, 4.3.0.13 |
| 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.705 <5.25.705.5, >=5.25.92 <5.25.92.84, >=7.0.78 <7.0.78.19 | 5.18.187.259, 5.23.8.180, 5.24.8.5, 5.25.705.5, 5.25.92.84, 7.0.78.19 |
| WSO2 | Carbon User Manager Kernel | >=4.10.9 <4.10.9.17, >=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.17, 4.6.1.114, 4.7.1.53, 4.8.1.16, 4.9.0.58, 4.9.26.7 |
| WSO2 | Identity Server | >=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 | 5.11.0.348, 6.0.0.194, 6.1.0.162, 7.0.0.33 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in WSO2, strongest first
Embed
A live severity badge for an advisory, README or ticket