CVE-2025-20389

4.3 MEDIUM

📋 TL;DR

A low-privileged user without admin or power roles can craft a malicious payload in the label column field when adding a new device in the Splunk Secure Gateway app, potentially causing client-side denial of service. This affects Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and Splunk Secure Gateway app versions below 3.9.10, 3.8.58, and 3.7.28 on Splunk Cloud Platform.

💻 Affected Systems

Products:
  • Splunk Enterprise
  • Splunk Secure Gateway app
Versions: Splunk Enterprise: below 10.0.2, 9.4.6, 9.3.8, 9.2.10; Splunk Secure Gateway app: below 3.9.10, 3.8.58, 3.7.28
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires Splunk Secure Gateway app installed and low-privileged user access to device management features.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Client-side DoS affecting user interface functionality for targeted users or groups, potentially disrupting monitoring or management operations.

🟠

Likely Case

Limited client-side disruption affecting individual users who encounter the malicious payload, with no server-side impact.

🟢

If Mitigated

Minimal impact if proper access controls limit low-privileged user access to device management features.

🌐 Internet-Facing: LOW - Exploitation requires authenticated low-privileged user access and targets client-side effects.
🏢 Internal Only: MEDIUM - Internal users with low privileges could disrupt client-side operations for themselves or others.

🎯 Exploit Status

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

Exploitation requires authenticated low-privileged user access and knowledge of payload crafting.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Splunk Enterprise: 10.0.2, 9.4.6, 9.3.8, 9.2.10; Splunk Secure Gateway app: 3.9.10, 3.8.58, 3.7.28

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

Restart Required: Yes

Instructions:

1. Download appropriate patched version from Splunk website. 2. Backup current installation. 3. Apply patch following Splunk upgrade procedures. 4. Restart Splunk services.

🔧 Temporary Workarounds

Restrict device management access

all

Limit low-privileged user access to Splunk Secure Gateway device management features.

splunk edit user <username> -role <restricted_role> -auth admin:changeme

🧯 If You Can't Patch

  • Implement strict access controls to prevent low-privileged users from accessing device management in Splunk Secure Gateway.
  • Monitor and audit device management activities for suspicious label field entries.

🔍 How to Verify

Check if Vulnerable:

Check Splunk version via web interface (Settings > Server settings) or CLI with 'splunk version', and verify Splunk Secure Gateway app version in Apps management.

Check Version:

splunk version

Verify Fix Applied:

Confirm version numbers meet or exceed patched versions: Splunk Enterprise >=10.0.2, 9.4.6, 9.3.8, or 9.2.10; Splunk Secure Gateway app >=3.9.10, 3.8.58, or 3.7.28.

📡 Detection & Monitoring

Log Indicators:

  • Unusual device additions with malformed label fields in Splunk Secure Gateway logs
  • User activity logs showing low-privileged users accessing device management

Network Indicators:

  • No specific network indicators as this is client-side

SIEM Query:

index=_internal source=*secure_gateway* "label" | search NOT label="*normal*" | stats count by user, label

🔗 References

📤 Share & Export