CVE-2024-5617

Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks

Published Nov 2, 2026 CVSS 3.1 · 4.8 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The flaw causes the account lockout logic to be applied only to the secondary user store when the same username exists in both primary and secondary stores, leaving the primary account open to repeated authentication attempts. This weakness, documented as CWE-799, allows an attacker who knows or guesses a username to bypass the intended lockout mechanism and try multiple passwords, potentially gaining unauthorized access to protected resources.

Affected Systems

The vulnerability affects all versions of WSO2 API Manager, WSO2 Carbon Identity Management, WSO2 Carbon User Manager Kernel and WSO2 Identity Server that have not applied the latest update. No specific product versions are listed, so any deployment of these products that remains uncompromised is considered at risk.

Risk and Exploitability

The CVSS score of 4.8 reflects a moderate severity; the EPSS score is unavailable and the issue is not listed in CISA KEV, indicating no confirmed widespread exploitation yet. However, the design flaw permits a straightforward brute‑force attack by repeatedly attempting login credentials against the primary user store, a scenario that is possible via any exposed authentication endpoint. Attackers only need valid user identifiers to exploit this bypass, making the vulnerability potentially impactful if adequate account lockout rates are not enforced elsewhere. Based on the description, the likely attack vector is any exposed authentication endpoint.

Remediation

Vendor Solution

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3414/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3414/#solution


OpenCVE Recommended Actions

  • Apply the update or patch as outlined in the WSO2 security advisory for the affected products
  • If a patch cannot be applied immediately, consider disabling or redesigning the secondary user store configuration that shares duplicate usernames with the primary store
  • Implement or tighten external rate limiting, IP banning, or account lockout settings on the authentication interface to slow brute‑force attempts until the patch is deployed

Generated by OpenCVE AI on November 2, 2026 at 07:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Wso2 api Manager
Wso2 identity Server
Vendors & Products Wso2 api Manager
Wso2 identity Server
Type Values Removed Values Added
Description 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.
Title Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks
First Time appeared Wso2
Wso2 wso2 Api Manager
Wso2 wso2 Carbon Identity Management
Wso2 wso2 Carbon User Manager Kernel
Wso2 wso2 Identity Server
Weaknesses CWE-799
CPEs cpe:2.3:a:wso2:wso2_api_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_carbon_identity_management:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_carbon_user_manager_kernel:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:*
Vendors & Products Wso2
Wso2 wso2 Api Manager
Wso2 wso2 Carbon Identity Management
Wso2 wso2 Carbon User Manager Kernel
Wso2 wso2 Identity Server
References
Metrics cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-799

    Improper Control of Interaction Frequency

Sources

Status
PUBLISHED
Assigner
WSO2
Published
Updated
Nov 2, 2026, 7:40 PM
Reserved
Jun 4, 2024, 6:07 AM
Status
Awaiting Analysis
Published
Nov 2, 2026, 6:17 AM
Modified
Nov 9, 2026, 10:10 AM