CVE-2021-33845 json
Username enumeration through lockout message in REST API
published 2022-05-06 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-20519
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
The Splunk Enterprise REST API allows enumeration of usernames via the lockout error message. The potential vulnerability impacts Splunk Enterprise instances before 8.1.7 when configured to repress verbose login errors.
Patch / fix
- splunk splunk 8.1.7
Exploit prediction
0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Splunk Splunk Enterprise
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
splunk.com
/en_us/product-security/announcements/svd-2022-0502.html
vendor-advisory
-
research.splunk.com
/application/splunk_user_enumeration_attempt/
vendor-advisory
Sources
- CVE List CVE-2021-33845
- NVD CVE-2021-33845
Fencer Vulns 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.