CVE-2024-6832 - Vulnerability Details

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

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.

Published: 2026-08-06

Score: 5.9 Medium

EPSS: < 1% Very Low

KEV: No

Impact:

Action:

Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

WSO2

WSO2 Enterprise Integrator

unaffected

Version	Status	Constraints
`0`	unknown	< 6.6.0
`6.6.0`	affected	< 6.6.0.229

WSO2

WSO2 API Control Plane

unaffected

Version	Status	Constraints
`0`	unknown	< 4.5.0
`4.5.0`	affected	< 4.5.0.40
`4.6.0`	affected	< 4.6.0.4
`4.6.0`	affected	< 4.6.0.5

WSO2

WSO2 Traffic Manager

unaffected

Version	Status	Constraints
`0`	unknown	< 4.5.0
`4.5.0`	affected	< 4.5.0.38
`4.6.0`	affected	< 4.6.0.4
`4.6.0`	affected	< 4.6.0.5

WSO2

WSO2 Universal Gateway

unaffected

Version	Status	Constraints
`0`	unknown	< 4.5.0
`4.5.0`	affected	< 4.5.0.38
`4.6.0`	affected	< 4.6.0.4
`4.6.0`	affected	< 4.6.0.5

WSO2

WSO2 API Manager

unaffected

Version	Status	Constraints
`0`	unknown	< 3.1.0
`3.1.0`	affected	< 3.1.0.296
`3.2.0`	affected	< 3.2.0.386
`3.2.0`	affected	< 3.2.0.455
`3.2.1`	affected	< 3.2.1.74
`4.1.0`	affected	< 4.1.0.238
`4.2.0`	affected	< 4.2.0.179
`4.3.0`	affected	< 4.3.0.91
`4.4.0`	affected	< 4.4.0.55
`4.5.0`	affected	< 4.5.0.39
`4.6.0`	affected	< 4.6.0.4

WSO2

WSO2 Identity Server

unaffected

Version	Status	Constraints
`0`	unknown	< 5.10.0
`5.10.0`	affected	< 5.10.0.320
`5.11.0`	affected	< 5.11.0.427
`6.0.0`	affected	< 6.0.0.254
`6.1.0`	affected	< 6.1.0.195
`7.0.0`	affected	< 7.0.0.82

WSO2

WSO2 Identity Server as Key Manager

unaffected

Version	Status	Constraints
`0`	unknown	< 5.10.0
`5.10.0`	affected	< 5.10.0.314

WSO2

WSO2 Open Banking IAM

unaffected

Version	Status	Constraints
`0`	unknown	< 2.0.0
`2.0.0`	affected	< 2.0.0.366

WSO2

WSO2 Open Banking AM

unaffected

Version	Status	Constraints
`0`	unknown	< 2.0.0
`2.0.0`	affected	< 2.0.0.345

WSO2

WSO2 Carbon User Manager Kernel

unknown

Version	Status	Constraints
`4.5.0`	affected	< 4.5.0.7
`4.5.3`	affected	< 4.5.3.53
`4.6.0`	affected	< 4.6.0.196
`4.6.1`	affected	< 4.6.1.163
`4.6.1`	affected	< 4.6.1.164
`4.6.3`	affected	< 4.6.3.44
`4.6.4`	affected	< 4.6.4.25
`4.7.1`	affected	< 4.7.1.77
`4.7.1`	affected	< 4.7.1.78
`4.8.1`	affected	< 4.8.1.46
`4.9.26`	affected	< 4.9.26.33
`4.9.27`	affected	< 4.9.27.19
`4.9.28`	affected	< 4.9.28.21
`4.9.33`	affected	< 4.9.33.4
`4.10.9`	affected	< 4.10.9.49
`x`	unaffected	≤ *

No data.

Vendor Product Confidence Versions

Wso2

Wso2 Api Control Plane

100%

Version	Status	Scheme	Platform
`[4.5.0,4.5.0.40)`	affected	generic	—
`[4.6.0,4.6.0.4)`	affected	generic	—
`[4.6.0,4.6.0.5)`	affected	generic	—

Wso2

Wso2 Api Manager

100%

Version	Status	Scheme	Platform
`[3.1.0,3.1.0.296)`	affected	generic	—
`[3.2.0,3.2.0.386)`	affected	generic	—
`[3.2.0,3.2.0.455)`	affected	generic	—
`[3.2.1,3.2.1.74)`	affected	generic	—
`[4.1.0,4.1.0.238)`	affected	generic	—
`[4.2.0,4.2.0.179)`	affected	generic	—
`[4.3.0,4.3.0.91)`	affected	generic	—
`[4.4.0,4.4.0.55)`	affected	generic	—
`[4.5.0,4.5.0.39)`	affected	generic	—
`[4.6.0,4.6.0.4)`	affected	generic	—

Wso2

Wso2 Carbon User Manager Kernel

100%

Version	Status	Scheme	Platform
`[4.5.0,4.5.0.7)`	affected	generic	—
`[4.5.3,4.5.3.53)`	affected	generic	—
`[4.6.0,4.6.0.196)`	affected	generic	—
`[4.6.1,4.6.1.163)`	affected	generic	—
`[4.6.1,4.6.1.164)`	affected	generic	—
`[4.6.3,4.6.3.44)`	affected	generic	—
`[4.6.4,4.6.4.25)`	affected	generic	—
`[4.7.1,4.7.1.77)`	affected	generic	—
`[4.7.1,4.7.1.78)`	affected	generic	—
`[4.8.1,4.8.1.46)`	affected	generic	—
`[4.9.26,4.9.26.33)`	affected	generic	—
`[4.9.27,4.9.27.19)`	affected	generic	—
`[4.9.28,4.9.28.21)`	affected	generic	—
`[4.9.33,4.9.33.4)`	affected	generic	—
`[4.10.9,4.10.9.49)`	affected	generic	—
`[x,*]`	unaffected	generic	—

Wso2

Wso2 Enterprise Integrator

100%

Version	Status	Scheme	Platform
`[6.6.0,6.6.0.229)`	affected	generic	—

Wso2

Wso2 Identity Server

100%

Version	Status	Scheme	Platform
`[3.1.0,3.1.0.296)`	affected	generic	—
`[3.2.0,3.2.0.386)`	affected	generic	—
`[3.2.0,3.2.0.455)`	affected	generic	—
`[3.2.1,3.2.1.74)`	affected	generic	—
`[4.1.0,4.1.0.238)`	affected	generic	—
`[4.2.0,4.2.0.179)`	affected	generic	—
`[4.3.0,4.3.0.91)`	affected	generic	—
`[4.4.0,4.4.0.55)`	affected	generic	—
`[4.5.0,4.5.0.39)`	affected	generic	—
`[4.6.0,4.6.0.4)`	affected	generic	—

Wso2

Wso2 Identity Server As Key Manager

100%

Version	Status	Scheme	Platform
`[5.10.0,5.10.0.314)`	affected	generic	—

Wso2

Wso2 Open Banking Am

100%

Version	Status	Scheme	Platform
`[2.0.0,2.0.0.345)`	affected	generic	—

Wso2

Wso2 Open Banking Iam

100%

Version	Status	Scheme	Platform
`[2.0.0,2.0.0.366)`	affected	generic	—

Wso2

Wso2 Traffic Manager

100%

Version	Status	Scheme	Platform
`[4.5.0,4.5.0.38)`	affected	generic	—
`[4.6.0,4.6.0.4)`	affected	generic	—
`[4.6.0,4.6.0.5)`	affected	generic	—

Wso2

Wso2 Universal Gateway

100%

Version	Status	Scheme	Platform
`[4.5.0,4.5.0.38)`	affected	generic	—
`[4.6.0,4.6.0.4)`	affected	generic	—
`[4.6.0,4.6.0.5)`	affected	generic	—

Found an issue or want to improve our Enrichment? You can suggest it directly by opening an issue on our dedicated GitHub repository .

Remediation

Vendor Solution

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

No CVSS v4.0

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact High

Integrity Impact None

Availability Impact None

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.00252.

Exploitation none

Automatable no

Technical Impact partial

References

Link	Providers
https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/

History

Fri, 07 Aug 2026 10:30:00 +0000

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

Thu, 06 Aug 2026 14:30:00 +0000

Type	Values Removed	Values Added
Metrics		ssvc `{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}`

Thu, 06 Aug 2026 08:15:00 +0000

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		https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/
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'}`

Subscriptions

Wso2 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 Wso2 Universal Gateway

MITRE

Status: PUBLISHED

Assigner: WSO2

Published: 2026-08-06T07:32:59.256Z

Updated: 2026-08-06T12:34:29.243Z

Reserved: 2024-07-17T11:44:02.821Z

Link: CVE-2024-6832

Vulnrichment

Updated: 2026-08-06T12:34:25.767Z

NVD

No data.

Redhat

No data.

OpenCVE Enrichment

Updated: 2026-08-07T10:04:33Z

Weaknesses

CWE-693

Tracking

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact High

Integrity Impact None

Availability Impact None

User Interaction None

Exploitation none

Automatable no

Technical Impact partial

Subscriptions

JSON object

JSON object

JSON object

JSON object

JSON object