WSO2 API Manager Account Lock Feature improper authentication

Summaryinfo

A vulnerability was found in WSO2 API Manager, Identity Server, Carbon Identity Management and Carbon User Manager Kernel. It has been rated as critical. The affected element is an unknown function of the component Account Lock Feature. Performing a manipulation results in improper authentication. This vulnerability is known as CVE-2024-5617. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in WSO2 API Manager, Identity Server, Carbon Identity Management and Carbon User Manager Kernel (version unknown). It has been classified as critical. This affects an unknown function of the component Account Lock Feature. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account. This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts.

The advisory is shared at security.docs.wso2.com. This vulnerability is uniquely identified as CVE-2024-5617 since 06/04/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 11/02/2026).

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-55832). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Automation Software

Vendor

• WSO2

Name

• API Manager
• Carbon Identity Management
• Carbon User Manager Kernel
• Identity Server

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion