CVE-2025-20388
Blind Server Side Request Forgery (SSRF) through Distributed Search Peers in Splunk Enterprise
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.0.1, 9.4.6, 9.3.8, 9.2.10, 10.1.2507.4, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In Splunk Enterprise versions below 10.0.1, 9.4.6, 9.3.8, and 9.2.10, and Splunk Cloud Platform versions below 10.1.2507.4, 10.0.2503.7, and 9.3.2411.116, a user who holds a role that contains the high privilege capability `change_authentication` could enumerate internal IP addresses and network ports when adding new search peers to a Splunk search head in a distributed environment.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Splunk Splunk Enterprise
From 10.0 · fixed in 10.0.1; From 9.4 · fixed in 9.4.6; From 9.3 · fixed in 9.3.8; From 9.2 · fixed in 9.2.10
- Splunk Splunk Cloud Platform
From 10.1.2507 · fixed in 10.1.2507.4; From 10.0.2503 · fixed in 10.0.2503.6; From 9.3.2411 · fixed in 9.3.2411.116