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.
References
| Link | Resource |
|---|---|
| https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/ | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-08-06 08:16
Updated : 2026-08-09 14:14
NVD link : CVE-2024-6832
Mitre link : CVE-2024-6832
CVE.ORG link : CVE-2024-6832
JSON object : View
Products Affected
wso2
- api_control_plane
- traffic_manager
- api_manager
- open_banking_iam
- universal_gateway
- identity_server_as_key_manager
- identity_server
- open_banking_am
CWE
CWE-693
Protection Mechanism Failure
