# CVE-2024-53243: Information Disclosure in Mobile Alert Responses in Splunk Secure Gateway

> Low-privileged users can view alert search query responses via KVstore endpoints due to improper access control in Splunk Secure Gateway.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2024
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-c93m-w54c-8g9x

## What is CVE-2024-53243?

CVE-2024-53243 is a medium-severity vulnerability in Splunk Enterprise, 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.2, 9.2.4, and 9.1.7 and versions below 3.2.462, 3.7.18, and 3.8.5 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could see alert search query responses using Splunk Secure Gateway App Key Value Store (KVstore) collections endpoints due to improper access control.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-53243?


## How do I fix CVE-2024-53243?

No fix has been published for CVE-2024-53243 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-53243 being exploited?

There is no known exploitation of CVE-2024-53243 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53243 and fix it if it is affected.

What it is: CVE-2024-53243 is a medium-severity vulnerability in Splunk Enterprise, published on 10 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53243 in the wild and no public exploit code.

Affected product: Splunk Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53243/ (Markdown: https://insights.sbomify.com/CVE-2024-53243/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53243
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53243
- OSV: https://osv.dev/vulnerability/CVE-2024-53243

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53243/
Summaries are generated and may contain mistakes; the official description above is the record.