# CVE-2024-23675: Splunk App Key Value Store (KV Store) Improper Handling of Permissions Leads to KV Store Collection Deletion

> Attackers can delete KV Store collections via the REST API due to improper permission handling in Splunk Enterprise.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 22 Jan 2024
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-h7m5-mp8f-v424

## What is CVE-2024-23675?

CVE-2024-23675 is a medium-severity missing authorization vulnerability in Splunk Splunk, published on 22 Jan 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.0.8 and 9.1.3, Splunk app key value store (KV Store) improperly handles permissions for users that use the REST application programming interface (API). This can potentially result in the deletion of KV Store collections.

Weakness: CWE-863 (Incorrect Authorization), CWE-284 (Improper Access Control)

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

It affects 2 products.


Products: Splunk Cloud, Splunk Splunk.

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

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

## Is CVE-2024-23675 being exploited?

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

## Other vulnerabilities in Splunk Splunk

- [CVE-2023-46214](https://insights.sbomify.com/CVE-2023-46214/): Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing (high 8.0)
- [CVE-2024-36982](https://insights.sbomify.com/CVE-2024-36982/): Denial of Service through null pointer reference in “cluster/config” REST endpoint (high 7.5)
- [CVE-2024-36989](https://insights.sbomify.com/CVE-2024-36989/): Low-privileged user could create notifications in Splunk Web Bulletin Messages (medium 6.5)
- [CVE-2024-36986](https://insights.sbomify.com/CVE-2024-36986/): Risky command safeguards bypass through Search ID query in Analytics Workspace (medium 6.3)
- [CVE-2023-46213](https://insights.sbomify.com/CVE-2023-46213/): Cross-site Scripting (XSS) on “Show Syntax Highlighted” View in Search Page (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23675 is a medium-severity missing authorization vulnerability in Splunk Splunk, published on 22 Jan 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-23675 in the wild and no public exploit code.

Affected product: Splunk Splunk. 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-23675/ (Markdown: https://insights.sbomify.com/CVE-2024-23675/index.md)
```

## Sources

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

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