CVE-2025-20366

6.5 MEDIUM

📋 TL;DR

A low-privileged user in Splunk Enterprise or Splunk Cloud Platform can access sensitive search results by guessing the unique Search ID (SID) of administrative background search jobs. This affects users without admin or power roles in vulnerable versions. The vulnerability allows unauthorized access to potentially confidential data.

💻 Affected Systems

Products:
  • Splunk Enterprise
  • Splunk Cloud Platform
Versions: Splunk Enterprise below 9.4.4, 9.3.6, and 9.2.8; Splunk Cloud Platform below 9.3.2411.111, 9.3.2408.119, and 9.2.2406.122
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires administrative search jobs running in background and low-privileged user access.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Sensitive data exposure including credentials, PII, or proprietary information from administrative search results accessed by unauthorized users.

🟠

Likely Case

Unauthorized access to search results containing operational data, configuration details, or limited sensitive information.

🟢

If Mitigated

Minimal impact with proper access controls, monitoring, and network segmentation in place.

🌐 Internet-Facing: MEDIUM - Exploitation requires authenticated access but could be combined with other vulnerabilities.
🏢 Internal Only: HIGH - Internal users with low privileges could access sensitive administrative search results.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires authenticated low-privileged user and ability to guess or discover SIDs.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Splunk Enterprise 9.4.4, 9.3.6, 9.2.8; Splunk Cloud Platform 9.3.2411.111, 9.3.2408.119, 9.2.2406.122

Vendor Advisory: https://advisory.splunk.com/advisories/SVD-2025-1001

Restart Required: Yes

Instructions:

1. Backup Splunk configuration and data. 2. Download appropriate patch version from Splunk downloads. 3. Stop Splunk services. 4. Install update following Splunk documentation. 5. Restart Splunk services. 6. Verify version and functionality.

🔧 Temporary Workarounds

Restrict administrative search jobs

all

Limit use of administrative search jobs in background or ensure they don't contain sensitive data.

Enhance access controls

all

Review and tighten role-based access controls for search functionality.

🧯 If You Can't Patch

  • Implement strict network segmentation to limit access to Splunk instances
  • Enhance monitoring and alerting for unusual search activity patterns

🔍 How to Verify

Check if Vulnerable:

Check Splunk version via web interface or CLI and compare against affected versions.

Check Version:

splunk version

Verify Fix Applied:

Confirm version is at or above patched versions and test access controls for search jobs.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to search jobs
  • Multiple failed SID guessing attempts
  • Access to search results by low-privileged users

Network Indicators:

  • Unusual search API calls from non-admin users
  • Patterns of SID enumeration attempts

SIEM Query:

index=_audit action=search user=* NOT (role=admin OR role=power) search_id=* | stats count by user, search_id

🔗 References

📤 Share & Export