CVE-2021-33845 Username enumeration through lockout message in REST API
Attackers can enumerate valid usernames via REST API lockout messages when verbose login errors are repressed, facilitating targeted attacks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2021-33845?
CVE-2021-33845 is a medium-severity vulnerability in Splunk Splunk, published on 6 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-203
Which versions are affected by CVE-2021-33845?
It affects 1 product.
Products include Splunk Splunk.
How do I fix CVE-2021-33845?
No fix has been published for CVE-2021-33845 yet. Limit exposure of the affected software until one is available.
Is CVE-2021-33845 being exploited?
There is no known exploitation of CVE-2021-33845 in the wild and no public exploit code.
Other vulnerabilities in Splunk Splunk
- CVE-2026-20253 Splunk Enterprise Missing Authentication for Critical Function
- CVE-2026-76268 Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise
- CVE-2026-76284 Improper Neutralization in Splunk Enterprise
- CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise
- CVE-2017-17067 Auth bypass in n/a
Sources
Also known as GHSA-8h69-rhj2-r69p.