CVE-2024-6832

Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks

Published Aug 6, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability arises when the account locking mechanism fails to trigger if secondary user stores are unavailable, enabling attackers to attempt unlimited authentication attempts against valid accounts in active stores. This flaw is classified as CWE-693, which stems from a failure to maintain consistent system state during lockout processing. The result is that user accounts remain susceptible to brute force attacks, potentially exposing credentials and increasing the risk of compromise.

Affected Systems

Affected products include WSO2 API Control Plane, WSO2 API Manager, WSO2 Carbon User Manager Kernel, WSO2 Enterprise Integrator, WSO2 Identity Server, WSO2 Identity Server as Key Manager, WSO2 Open Banking AM, WSO2 Open Banking IAM, WSO2 Traffic Manager, and WSO2 Universal Gateway. Version information is not specified.

Risk and Exploitability

The CVSS score is 5.9, indicating medium severity, and the EPSS score is not available. It is not listed in CISA's KEV catalog. It is inferred that the exploit requires remote network access to the authentication interfaces and depends on the presence of enabled secondary user stores. Because the lockout counter is never incremented when secondary stores fail, an attacker can repeatedly submit invalid credentials without triggering the lockout, making brute force attacks feasible with sufficient time and bandwidth. While there is no known active exploitation, the conditions for exploitation are straightforward, so the potential risk remains tangible.

Remediation

Vendor Solution

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


OpenCVE Recommended Actions

  • Update all WSO2 products to the latest released patch, following the instructions in the advisory at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/#solution.
  • Confirm that all configured secondary user stores are operational and reachable. Implement monitoring or alerting to detect any connectivity issues before authentication requests fail.
  • Implement additional lockout policies or enforce multi-factor authentication in your deployment to add a compensating control against brute‑force attempts.

Generated by OpenCVE AI on August 6, 2026 at 10:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wso2
Wso2 wso2 Api Control Plane
Wso2 wso2 Api Manager
Wso2 wso2 Carbon User Manager Kernel
Wso2 wso2 Enterprise Integrator
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
Wso2 wso2 Traffic Manager
Wso2 wso2 Universal Gateway
Vendors & Products Wso2
Wso2 wso2 Api Control Plane
Wso2 wso2 Api Manager
Wso2 wso2 Carbon User Manager Kernel
Wso2 wso2 Enterprise Integrator
Wso2 wso2 Identity Server
Wso2 wso2 Identity Server As Key Manager
Wso2 wso2 Open Banking Am
Wso2 wso2 Open Banking Iam
Wso2 wso2 Traffic Manager
Wso2 wso2 Universal Gateway
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description 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.
Title Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks
Weaknesses CWE-693
References
Metrics cvssV3_1

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