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.
Project Subscriptions
| Vendors | Products |
|---|---|
|
Wso2
Subscribe
|
Wso2 Api Control Plane
Subscribe
Wso2 Api Manager
Subscribe
Wso2 Carbon User Manager Kernel
Subscribe
Wso2 Enterprise Integrator
Subscribe
Wso2 Identity Server
Subscribe
Wso2 Identity Server As Key Manager
Subscribe
Wso2 Open Banking Am
Subscribe
Wso2 Open Banking Iam
Subscribe
Wso2 Traffic Manager
Subscribe
Wso2 Universal Gateway
Subscribe
|
No advisories yet.
Solution
Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/#solution
Workaround
No workaround given by the vendor.
Fri, 07 Aug 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wso2
Wso2 wso2 Api Control Plane Wso2 wso2 Api Manager Wso2 wso2 Carbon User Manager Kernel Wso2 wso2 Enterprise Integrator Wso2 wso2 Identity Server Wso2 wso2 Identity Server As Key Manager Wso2 wso2 Open Banking Am Wso2 wso2 Open Banking Iam Wso2 wso2 Traffic Manager Wso2 wso2 Universal Gateway |
|
| Vendors & Products |
Wso2
Wso2 wso2 Api Control Plane Wso2 wso2 Api Manager Wso2 wso2 Carbon User Manager Kernel Wso2 wso2 Enterprise Integrator Wso2 wso2 Identity Server Wso2 wso2 Identity Server As Key Manager Wso2 wso2 Open Banking Am Wso2 wso2 Open Banking Iam Wso2 wso2 Traffic Manager Wso2 wso2 Universal Gateway |
Thu, 06 Aug 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 06 Aug 2026 08:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks | |
| Weaknesses | CWE-693 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: WSO2
Published:
Updated: 2026-08-06T12:34:29.243Z
Reserved: 2024-07-17T11:44:02.821Z
Link: CVE-2024-6832
Updated: 2026-08-06T12:34:25.767Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-08-07T10:04:33Z