Account Lockout Failure via Secondary User Store Inaccessibility 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 Control Plane 4.5.0.40, API Control Plane 4.6.0.4, API Control Plane 4.6.0.5 and 40 more.
The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without triggering the lockout mechanism for users within active stores. When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| WSO2 | API Control Plane | >=4.5.0 <4.5.0.40, >=4.6.0 <4.6.0.4, >=4.6.0 <4.6.0.5 | 4.5.0.40, 4.6.0.4, 4.6.0.5 |
| WSO2 | API Manager | >=3.1.0 <3.1.0.296, >=3.2.0 <3.2.0.386, >=3.2.0 <3.2.0.455, >=3.2.1 <3.2.1.74, >=4.1.0 <4.1.0.238, >=4.2.0 <4.2.0.179, >=4.3.0 <4.3.0.91, >=4.4.0 <4.4.0.55, >=4.5.0 <4.5.0.39, >=4.6.0 <4.6.0.4 | 3.1.0.296, 3.2.0.386, 3.2.0.455, 3.2.1.74, 4.1.0.238, 4.2.0.179, 4.3.0.91, 4.4.0.55, 4.5.0.39, 4.6.0.4 |
| WSO2 | Carbon User Manager Kernel | >=4.10.9 <4.10.9.49, >=4.5.0 <4.5.0.7, >=4.5.3 <4.5.3.53, >=4.6.0 <4.6.0.196, >=4.6.1 <4.6.1.163, >=4.6.1 <4.6.1.164, >=4.6.3 <4.6.3.44, >=4.6.4 <4.6.4.25, >=4.7.1 <4.7.1.77, >=4.7.1 <4.7.1.78, >=4.8.1 <4.8.1.46, >=4.9.26 <4.9.26.33, >=4.9.27 <4.9.27.19, >=4.9.28 <4.9.28.21, >=4.9.33 <4.9.33.4 | 4.10.9.49, 4.5.0.7, 4.5.3.53, 4.6.0.196, 4.6.1.163, 4.6.1.164, 4.6.3.44, 4.6.4.25, 4.7.1.77, 4.7.1.78, 4.8.1.46, 4.9.26.33, 4.9.27.19, 4.9.28.21, 4.9.33.4 |
| WSO2 | Enterprise Integrator | >=6.6.0 <6.6.0.229 | 6.6.0.229 |
| WSO2 | Identity Server | >=5.10.0 <5.10.0.314, >=5.10.0 <5.10.0.320, >=5.11.0 <5.11.0.427, >=6.0.0 <6.0.0.254, >=6.1.0 <6.1.0.195, >=7.0.0 <7.0.0.82 | 5.10.0.314, 5.10.0.320, 5.11.0.427, 6.0.0.254, 6.1.0.195, 7.0.0.82 |
| WSO2 | Open Banking AM | >=2.0.0 <2.0.0.345 | 2.0.0.345 |
| WSO2 | Open Banking IAM | >=2.0.0 <2.0.0.366 | 2.0.0.366 |
| WSO2 | Traffic Manager | >=4.5.0 <4.5.0.38, >=4.6.0 <4.6.0.4, >=4.6.0 <4.6.0.5 | 4.5.0.38, 4.6.0.4, 4.6.0.5 |
| WSO2 | Universal Gateway | >=4.5.0 <4.5.0.38, >=4.6.0 <4.6.0.4, >=4.6.0 <4.6.0.5 | 4.5.0.38, 4.6.0.4, 4.6.0.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in WSO2, strongest first
Embed
A live severity badge for an advisory, README or ticket