What is the severity of CVE-2014-8380?

CVE-2014-8380 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.

How do I fix CVE-2014-8380?

To fix CVE-2014-8380, it is recommended to upgrade Splunk to a version that is not affected by this vulnerability.

Who is affected by CVE-2014-8380?

CVE-2014-8380 affects users of Splunk version 6.1.1.

What type of vulnerability is CVE-2014-8380?

CVE-2014-8380 is a cross-site scripting (XSS) vulnerability.

What conditions must be met for CVE-2014-8380 to be exploited?

CVE-2014-8380 can be exploited when an attacker injects arbitrary web script or HTML via the HTTP Referer Header in a "404 Not Found" response.

Vulnerability/
CVE-2014-8380

medium

4.3

CWE

21/10/2014

6/8/2024

CVE-2014-8380: XSS

First published: Tue Oct 21 2014(Updated: )

Cross-site scripting (XSS) vulnerability in Splunk 6.1.1 allows remote attackers to inject arbitrary web script or HTML via the HTTP Referer Header in a "404 Not Found" response. NOTE: this vulnerability might exist because of a CVE-2010-2429 regression.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Splunk Splunk	=6.1.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2014-8380?
CVE-2014-8380 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2014-8380?
To fix CVE-2014-8380, it is recommended to upgrade Splunk to a version that is not affected by this vulnerability.
Who is affected by CVE-2014-8380?
CVE-2014-8380 affects users of Splunk version 6.1.1.
What type of vulnerability is CVE-2014-8380?
CVE-2014-8380 is a cross-site scripting (XSS) vulnerability.
What conditions must be met for CVE-2014-8380 to be exploited?
CVE-2014-8380 can be exploited when an attacker injects arbitrary web script or HTML via the HTTP Referer Header in a "404 Not Found" response.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/references
agent/severity
agent/last-modified-date
agent/author
agent/event
agent/description
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/splunk
canonical/splunk splunk
version/splunk splunk/6.1.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2014-8380?
CVE-2014-8380 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2014-8380?
To fix CVE-2014-8380, it is recommended to upgrade Splunk to a version that is not affected by this vulnerability.
Who is affected by CVE-2014-8380?
CVE-2014-8380 affects users of Splunk version 6.1.1.
What type of vulnerability is CVE-2014-8380?
CVE-2014-8380 is a cross-site scripting (XSS) vulnerability.
What conditions must be met for CVE-2014-8380 to be exploited?
CVE-2014-8380 can be exploited when an attacker injects arbitrary web script or HTML via the HTTP Referer Header in a "404 Not Found" response.