WSO2 API Control Plane Account Locking Mechanism locking

Summaryinfo

A vulnerability identified as very critical has been detected in WSO2 API Control Plane, API Manager, Carbon User Manager Kernel, Enterprise Integrator, Identity Server, Identity Server as Key Manager, Open Banking AM, Open Banking IAM, Traffic Manager and Universal Gateway. This vulnerability affects unknown code of the component Account Locking Mechanism. This manipulation causes locking. This vulnerability is handled as CVE-2024-6832. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in WSO2 API Control Plane, API Manager, Carbon User Manager Kernel, Enterprise Integrator, Identity Server, Identity Server as Key Manager, Open Banking AM, Open Banking IAM, Traffic Manager and Universal Gateway. It has been declared as very critical. Affected by this vulnerability is some unknown functionality of the component Account Locking Mechanism. The manipulation with an unknown input leads to a locking vulnerability. The CWE definition for the vulnerability is CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at security.docs.wso2.com. This vulnerability is known as CVE-2024-6832 since 07/17/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/06/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Banking Software

Vendor

• WSO2

Name

• API Control Plane
• API Manager
• Carbon User Manager Kernel
• Enterprise Integrator
• Identity Server
• Identity Server as Key Manager
• Open Banking AM
• Open Banking IAM
• Traffic Manager
• Universal Gateway

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion