CVE-2016-4859
Last modified
CVE-2016-4859 is a vulnerability of currently unknown severity. Open redirect vulnerability in Splunk Enterprise 6.4.x prior to 6.4.3, Splunk Enterprise 6.3.x prior to 6.3.6, Splunk Enterprise 6.2.x prior to 6.2.10, Splunk Enterprise 6.1.x prior to 6.1.11, Splunk Enterprise 6.0.x prior to 6.0.12, Splunk Enterprise 5.0.x prior to 5.0.16 and Splunk Light prior to 6.4.3 allows to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.. EPSS estimates a 1.43% chance of exploitation in the next 30 days.
Description
Open redirect vulnerability in Splunk Enterprise 6.4.x prior to 6.4.3, Splunk Enterprise 6.3.x prior to 6.3.6, Splunk Enterprise 6.2.x prior to 6.2.10, Splunk Enterprise 6.1.x prior to 6.1.11, Splunk Enterprise 6.0.x prior to 6.0.12, Splunk Enterprise 5.0.x prior to 5.0.16 and Splunk Light prior to 6.4.3 allows to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk | <= 6.4.2 |
| Splunk | Splunk | 5.0.0 |
| Splunk | Splunk | 5.0.1 |
| Splunk | Splunk | 5.0.2 |
| Splunk | Splunk | 5.0.3 |
| Splunk | Splunk | 5.0.4 |
| Splunk | Splunk | 5.0.5 |
| Splunk | Splunk | 5.0.6 |
| Splunk | Splunk | 5.0.7 |
| Splunk | Splunk | 5.0.8 |
| Splunk | Splunk | 5.0.9 |
| Splunk | Splunk | 5.0.10 |
| Splunk | Splunk | 5.0.11 |
| Splunk | Splunk | 5.0.12 |
| Splunk | Splunk | 5.0.13 |
| Splunk | Splunk | 5.0.14 |
| Splunk | Splunk | 5.0.15 |
| Splunk | Splunk | 6.0.0 |
| Splunk | Splunk | 6.0.1 |
| Splunk | Splunk | 6.0.2 |
| Splunk | Splunk | 6.0.3 |
| Splunk | Splunk | 6.0.4 |
| Splunk | Splunk | 6.0.5 |
| Splunk | Splunk | 6.0.6 |
| Splunk | Splunk | 6.0.7 |
| Splunk | Splunk | 6.0.8 |
| Splunk | Splunk | 6.0.9 |
| Splunk | Splunk | 6.0.10 |
| Splunk | Splunk | 6.0.11 |
| Splunk | Splunk | 6.1.0 |
| Splunk | Splunk | 6.1.1 |
| Splunk | Splunk | 6.1.2 |
| Splunk | Splunk | 6.1.3 |
| Splunk | Splunk | 6.1.4 |
| Splunk | Splunk | 6.1.5 |
| Splunk | Splunk | 6.1.6 |
| Splunk | Splunk | 6.1.7 |
| Splunk | Splunk | 6.1.8 |
| Splunk | Splunk | 6.1.9 |
| Splunk | Splunk | 6.1.10 |
| Splunk | Splunk | 6.2.0 |
| Splunk | Splunk | 6.2.1 |
| Splunk | Splunk | 6.2.2 |
| Splunk | Splunk | 6.2.3 |
| Splunk | Splunk | 6.2.4 |
| Splunk | Splunk | 6.2.5 |
| Splunk | Splunk | 6.2.6 |
| Splunk | Splunk | 6.2.7 |
| Splunk | Splunk | 6.2.8 |
| Splunk | Splunk | 6.2.9 |
Showing 50 of 58 affected configurations. See NVD for the full list.
References
- http://www.securityfocus.com/bid/92603Third Party Advisory, VDB Entry
- https://jvn.jp/en/jp/JVN64800312/index.htmlThird Party Advisory, VDB Entry
- https://www.splunk.com/view/SP-CAAAPQ6Vendor Advisory
- http://www.securityfocus.com/bid/92603Third Party Advisory, VDB Entry
- https://jvn.jp/en/jp/JVN64800312/index.htmlThird Party Advisory, VDB Entry
- https://www.splunk.com/view/SP-CAAAPQ6Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-4859?
How severe is CVE-2016-4859?
How do I fix CVE-2016-4859?
Are you affected by CVE-2016-4859?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
