Skip to content
Fencer Intel
medium 5.9

CVE-2024-6832 json

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

published 3mo ago modified 15d ago also EUVD-2024-55707

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

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.

Patch / fix

  • WSO2 WSO2 Enterprise Integrator 6.6.0.229
  • WSO2 WSO2 API Control Plane 4.5.0.40, 4.6.0.4, 4.6.0.5
  • WSO2 WSO2 Traffic Manager 4.5.0.38, 4.6.0.4, 4.6.0.5
  • WSO2 WSO2 Universal Gateway 4.5.0.38, 4.6.0.4, 4.6.0.5
  • WSO2 WSO2 API Manager 3.1.0.296, 3.2.0.386, 3.2.0.455, 3.2.1.74, 4.1.0.238, 4.2.0.179, 4.3.0.91, 4.4.0.55, 4.5.0.39, 4.6.0.4
  • WSO2 WSO2 Identity Server 5.10.0.320, 5.11.0.427, 6.0.0.254, 6.1.0.195, 7.0.0.82
  • WSO2 WSO2 Identity Server as Key Manager 5.10.0.314
  • WSO2 WSO2 Open Banking IAM 2.0.0.366
  • WSO2 WSO2 Open Banking AM 2.0.0.345
  • WSO2 WSO2 Carbon User Manager Kernel 4.5.0.7, 4.5.3.53, 4.6.0.196, 4.6.1.163, 4.6.1.164, 4.6.3.44, 4.6.4.25, 4.7.1.77, 4.7.1.78, 4.8.1.46, 4.9.26.33, 4.9.27.19, 4.9.28.21, 4.9.33.4, 4.10.9.49

Is CVE-2024-6832 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

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

Classification

Weakness
  • CWE-693 Protection Mechanism Failure

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.