A vulnerability classified as critical has been found in Splunk Enterprise Server up to 6.4.x (Log Management Software). Affected is some unknown processing. The manipulation of the argument alerts_id with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was released 12/09/2016 by Francesco Oddo with Security-Assessment as Splunk Enterprise Server-Side Request Forgery as not defined mailinglist post (Full-Disclosure). The advisory is available at seclists.org. The public release was coordinated with the vendor. It is possible to launch the attack remotely. Technical details and a public exploit are known. The advisory points out:

A server-side request forgery (SSRF) vulnerability exists in the Splunk Enterprise web management interface within the Alert functionality. The application parses user supplied data in the GET parameter ‘alerts_id’ to construct a HTTP request to the splunkd daemon listening on TCP port 8089. Since no validation is carried out on the parameter, an attacker can specify an external domain and force the application to make a HTTP request to an arbitrary destination host. The issue is aggravated by the fact that the application includes the REST API token for the currently authenticated user within the Authorization request header.

A public exploit has been developed by Francesco Oddo in Python and been published immediately after the advisory. The exploit is shared for download at seclists.org. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 78 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 6.5.0 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

Productinfo

Type

• Log Management Software

Vendor

• Splunk

Name

• Enterprise Server

Version

• 6.0
• 6.1
• 6.2
• 6.3
• 6.4

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion