Sensitive Information Disclosure in ''_internal'' index in Splunk Enterprise
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
Splunk Enterprise · Splunk Cloud Platform
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
| No fix yet |
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.
From the CVE record · cisco
In affected Splunk Search Head Cluster deployments, conf.log can contain SAML configurations for Attribute query requests or Authentication extensions in plain text, depending on which feature is configured. A user with a role that can access the Splunk _internal index can view those configurations; no other user interaction is described.
Operators of Splunk Enterprise below 10.2.0, 10.0.2, 9.4.7, 9.3.8, or 9.2.11, or Splunk Cloud Platform below 10.2.2510.0, 10.1.2507.11, 10.0.2503.9, or 9.3.2411.120, should check their Search Head Cluster deployments.