Vulnerability Details CVE-2024-6832
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.003
EPSS Ranking 16.5%
CVSS Severity
CVSS v3 Score 5.9
Products affected by CVE-2024-6832
-
cpe:2.3:a:wso2:api_control_plane:4.5.0
-
cpe:2.3:a:wso2:api_control_plane:4.6.0
-
cpe:2.3:a:wso2:api_manager:3.1.0
-
cpe:2.3:a:wso2:api_manager:3.2.0
-
cpe:2.3:a:wso2:api_manager:3.2.1
-
cpe:2.3:a:wso2:api_manager:4.1.0
-
cpe:2.3:a:wso2:api_manager:4.2.0
-
cpe:2.3:a:wso2:api_manager:4.3.0
-
cpe:2.3:a:wso2:api_manager:4.4.0
-
cpe:2.3:a:wso2:api_manager:4.5.0
-
cpe:2.3:a:wso2:api_manager:4.6.0
-
cpe:2.3:a:wso2:identity_server:5.10.0
-
cpe:2.3:a:wso2:identity_server:5.11.0
-
cpe:2.3:a:wso2:identity_server:6.0.0
-
cpe:2.3:a:wso2:identity_server:6.1.0
-
cpe:2.3:a:wso2:identity_server:7.0.0
-
cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0
-
cpe:2.3:a:wso2:open_banking_am:2.0.0
-
cpe:2.3:a:wso2:open_banking_iam:2.0.0
-
cpe:2.3:a:wso2:traffic_manager:4.5.0
-
cpe:2.3:a:wso2:traffic_manager:4.6.0
-
cpe:2.3:a:wso2:universal_gateway:4.5.0
-
cpe:2.3:a:wso2:universal_gateway:4.6.0