Sensitive Information Disclosure in ''_internal'' index 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.2, 9.4.7, 9.3.8, 9.2.11, 10.1.2507.11, 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In Splunk Enterprise versions below 10.2.0, 10.0.2, 9.4.7, 9.3.8, and 9.2.11, and Splunk Cloud Platform versions below 10.2.2510.0, 10.1.2507.11, 10.0.2503.9, and 9.3.2411.120, a user of a Splunk Search Head Cluster (SHC) deployment who holds a role with access to the the Splunk _internal index could view the Security Assertion Markup Language (SAML) configurations for Attribute query requests (AQRs) or Authentication extensions in plain text within the conf.log file, depending on which feature is configured.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Splunk Splunk Enterprise
From 10.0 · fixed in 10.0.2; From 9.4 · fixed in 9.4.7; From 9.3 · fixed in 9.3.8; From 9.2 · fixed in 9.2.11
- Splunk Splunk Cloud Platform
From 10.1.2507 · fixed in 10.1.2507.11; From 10.0.2503 · fixed in 10.0.2503.9; From 9.3.2411 · fixed in 9.3.2411.120