CVE-2024-6832Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks
- 5.9MediumCVSS base score
- 0.41%Exploitation in 30 daysEPSS · top 64% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By WSO2
- 2 years later
· 2 years later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| WSO2CNA (assigner) | 3.1 | Medium5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVDNVD · Analyzed | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
- EPSS (exploitation in 30 days)
- 0.41% · top 64% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.9.
Affected products
WSO2 · WSO2 Enterprise Integrator
- unknown < 6.6.0
- affected 6.6.0 – < 6.6.0.229
- unknown < 4.5.0
- affected 4.5.0 – < 4.5.0.40
- affected 4.6.0 – < 4.6.0.4
- affected 4.6.0 – < 4.6.0.5
- unknown < 4.5.0
- affected 4.5.0 – < 4.5.0.38
- affected 4.6.0 – < 4.6.0.4
- affected 4.6.0 – < 4.6.0.5
- unknown < 4.5.0
- affected 4.5.0 – < 4.5.0.38
- affected 4.6.0 – < 4.6.0.4
- affected 4.6.0 – < 4.6.0.5
- unknown < 3.1.0
- affected 3.1.0 – < 3.1.0.296
- affected 3.2.0 – < 3.2.0.386
- affected 3.2.0 – < 3.2.0.455
- affected 3.2.1 – < 3.2.1.74
- affected 4.1.0 – < 4.1.0.238
- affected 4.2.0 – < 4.2.0.179
- affected 4.3.0 – < 4.3.0.91
- affected 4.4.0 – < 4.4.0.55
- affected 4.5.0 – < 4.5.0.39
- affected 4.6.0 – < 4.6.0.4
- unknown < 5.10.0
- affected 5.10.0 – < 5.10.0.320
- affected 5.11.0 – < 5.11.0.427
- affected 6.0.0 – < 6.0.0.254
- affected 6.1.0 – < 6.1.0.195
- affected 7.0.0 – < 7.0.0.82
WSO2 · WSO2 Identity Server as Key Manager
- unknown < 5.10.0
- affected 5.10.0 – < 5.10.0.314
- unknown < 2.0.0
- affected 2.0.0 – < 2.0.0.366
- unknown < 2.0.0
- affected 2.0.0 – < 2.0.0.345
WSO2 · WSO2 Carbon User Manager Kernel
- affected 4.5.0 – < 4.5.0.7
- affected 4.5.3 – < 4.5.3.53
- affected 4.6.0 – < 4.6.0.196
- affected 4.6.1 – < 4.6.1.163
- affected 4.6.1 – < 4.6.1.164
- affected 4.6.3 – < 4.6.3.44
- affected 4.6.4 – < 4.6.4.25
- affected 4.7.1 – < 4.7.1.77
- affected 4.7.1 – < 4.7.1.78
- affected 4.8.1 – < 4.8.1.46
- affected 4.9.26 – < 4.9.26.33
- affected 4.9.27 – < 4.9.27.19
- affected 4.9.28 – < 4.9.28.21
- affected 4.9.33 – < 4.9.33.4
- affected 4.10.9 – < 4.10.9.49
- unaffected x – ≤ *
What to do
Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3352/#solution
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-55707 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-6832)Record last updated .