| Package | Affected versions | Patched versions |
|---|---|---|
| splunk | ≥ 10.0.0, < 10.0.9≥ 10.2.0, < 10.2.6≥ 10.4.0, < 10.4.2≥ 9.4.0, < 9.4.14 | 10.0.910.2.610.4.29.4.14 |
| splunk secure gateway | ≥ 3.10.0, < 3.10.9≥ 3.8.0, < 3.8.70≥ 3.9.0, < 3.9.23 | 3.10.93.8.703.9.23 |
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.9, 3.9.23, and 3.8.70, a user who does not hold the "admin" or "power" Splunk roles could use Server-Side Request Forgery (SSRF) in report notifications to send system-authenticated requests to internal Splunk services, which could allow for changes to Search Head Cluster state and a denial of service. The vulnerability is possible because Splunk Secure Gateway does not validate report notification path values before it sends internal requests.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free