NetSight
medium5.9

CVE-2024-6832

The account locking mechanism fails to trigger when secondary user stores are inaccessible.

Impact

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 products

VendorProductAffected versions
Wso2Api Control Plane
Versions 4.5.0, 4.6.0
Wso2Api Manager
Versions 3.1.0, 3.2.0, 3.2.1, 4.1.0, 4.2.0, 4.3.0
Wso2Identity Server
Versions 5.10.0, 5.11.0, 6.0.0, 6.1.0, 7.0.0
Wso2Identity Server As Key Manager
Version 5.10.0
Wso2Open Banking Am
Version 2.0.0
Wso2Open Banking Iam
Version 2.0.0
Wso2Traffic Manager
Versions 4.5.0, 4.6.0
Wso2Universal Gateway
Versions 4.5.0, 4.6.0

Weakness classification

References