CVE-2024-53245 Information Disclosure due to Username Collision with a Role that has the same Name as the User
Low-privileged users can view dashboard names and XML by exploiting username collisions with read-access roles in Splunk Enterprise.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-53245?
CVE-2024-53245 is a low-severity vulnerability in Splunk Splunk, published on 10 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In Splunk Enterprise versions below 9.3.0, 9.2.4, and 9.1.7 and Splunk Cloud Platform versions below 9.1.2312.206, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles, that has a username with the same name as a role with read access to dashboards, could see the dashboard name and the dashboard XML by cloning the dashboard.
Weakness: CWE-200
Which versions are affected by CVE-2024-53245?
It affects 2 products.
Products include Splunk Splunk, Splunk Splunk Cloud Platform.
How do I fix CVE-2024-53245?
No fix has been published for CVE-2024-53245 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-53245 being exploited?
There is no known exploitation of CVE-2024-53245 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-qp49-g67r-vh5q.