Skip to content
OpenAdvisories
Medium · 4.8 CVE-2024-5617 EUVD-2024-55832GHSA-wxh9-84jx-g888

Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks

Published Nov 2, 2026 · Updated Nov 2, 2026 · Assigned by WSO2

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.

Affected products

VendorProductAffectedFixed
WSO2 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
WSO2 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
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 5.18.187.259
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 4.6.1.114

References