Security Advisory WSO2-2024-3352/CVE-2024-6832¶
Published: 2026-05-03
Version: 1.0.0
Severity: Medium
CVSS Score: 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)
CVE IDs: CVE-2024-6832
AFFECTED PRODUCTS¶
- WSO2 API Control Plane: 4.6.0, 4.5.0
- WSO2 API Manager: 4.6.0, 4.5.0, 4.4.0, 4.3.0, 4.2.0, 4.1.0, 3.2.1, 3.2.0, 3.1.0
- WSO2 Enterprise Integrator: 6.6.0
- WSO2 Identity Server as Key Manager: 5.10.0
- WSO2 Identity Server: 7.0.0, 6.1.0, 6.0.0, 5.11.0, 5.10.0
- WSO2 Open Banking AM: 2.0.0
- WSO2 Open Banking IAM: 2.0.0
- WSO2 Traffic Manager: 4.6.0, 4.5.0
- WSO2 Universal Gateway: 4.6.0, 4.5.0
OVERVIEW¶
Account locking mechanism fails when secondary user stores are inaccessible.
DESCRIPTION¶
When secondary user stores are configured the account locking mechanism may fail if one or more of these stores become inaccessible. In particular if a user from an active user store attempts to authenticate with an invalid password their account will not be locked even though the account lock feature is enabled for invalid password attempts.
IMPACT¶
When the account locking mechanism fails due to the inaccessibility of secondary user stores users in active user stores are left vulnerable to brute force attacks. Consequently a malicious actor could repeatedly attempt to authenticate with invalid passwords without the risk of triggering an account lock.
SOLUTION¶
Community Users (Open Source)¶
Apply the relevant fixes to your product using the public fix(es) provided below.
- https://github.com/wso2/carbon-kernel/pull/4045
- https://github.com/wso2/carbon-kernel/pull/3632
- https://github.com/wso2/carbon-kernel/pull/4031
If applying the fix or update is not feasible, migrate to the latest unaffected version of the respective WSO2 product(s).
Support Subscription Holders¶
Update your product to the specified update level, or to a higher update level, to mitigate the identified vulnerability.
Info
WSO2 Support Subscription Holders may use WSO2 Updates in order to apply the fix.
| Product Name | Product Version | Update Level |
|---|---|---|
| WSO2 API Control Plane | 4.6.0 | 4 |
| WSO2 API Control Plane | 4.6.0 | 5 |
| WSO2 API Control Plane | 4.5.0 | 40 |
| WSO2 API Manager | 4.6.0 | 4 |
| WSO2 API Manager | 4.5.0 | 39 |
| WSO2 API Manager | 4.4.0 | 55 |
| WSO2 API Manager | 4.3.0 | 91 |
| WSO2 API Manager | 4.2.0 | 179 |
| WSO2 API Manager | 4.1.0 | 238 |
| WSO2 API Manager | 3.2.1 | 74 |
| WSO2 API Manager | 3.2.0 | 386 |
| WSO2 API Manager | 3.2.0 | 455 |
| WSO2 API Manager | 3.1.0 | 296 |
| WSO2 Enterprise Integrator | 6.6.0 | 229 |
| WSO2 Identity Server | 7.0.0 | 82 |
| WSO2 Identity Server | 6.1.0 | 195 |
| WSO2 Identity Server | 6.0.0 | 254 |
| WSO2 Identity Server | 5.11.0 | 427 |
| WSO2 Identity Server | 5.10.0 | 320 |
| WSO2 Identity Server as Key Manager | 5.10.0 | 314 |
| WSO2 Open Banking AM | 2.0.0 | 345 |
| WSO2 Open Banking IAM | 2.0.0 | 366 |
| WSO2 Traffic Manager | 4.6.0 | 4 |
| WSO2 Traffic Manager | 4.6.0 | 5 |
| WSO2 Traffic Manager | 4.5.0 | 38 |
| WSO2 Universal Gateway | 4.6.0 | 4 |
| WSO2 Universal Gateway | 4.6.0 | 5 |
| WSO2 Universal Gateway | 4.5.0 | 38 |
NOTE¶
This vulneravility fix may break the existing deployment due to changes in the API response behavior. To avoid this, the following configuration can be used. However, it is important to note that by applying the below-mentioned configurations, you are re-enabling vulnerable behavior. Therefore, it is recommended to use these configurations only until the new behavior changes introduced with this update are adopted into the environments.
[user_store_commons]
enable_circuit_breaker_for_user_stores = false