First published: Tue Sep 14 2010(Updated: )
Splunk 4.0.0 through 4.1.4 allows remote attackers to conduct session hijacking attacks and obtain the splunkd session key via vectors related to the SPLUNKD_SESSION_KEY parameter.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Splunk | =4.0 | |
Splunk | =4.0.1 | |
Splunk | =4.0.2 | |
Splunk | =4.0.3 | |
Splunk | =4.0.4 | |
Splunk | =4.0.5 | |
Splunk | =4.0.6 | |
Splunk | =4.0.7 | |
Splunk | =4.0.8 | |
Splunk | =4.0.9 | |
Splunk | =4.0.10 | |
Splunk | =4.0.11 | |
Splunk | =4.1 | |
Splunk | =4.1.1 | |
Splunk | =4.1.2 | |
Splunk | =4.1.3 | |
Splunk | =4.1.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-3323 is rated as medium severity due to its potential for session hijacking.
To mitigate CVE-2010-3323, upgrade to a patched version of Splunk that is not affected, preferably 4.1.5 or higher.
CVE-2010-3323 affects Splunk versions 4.0.0 through 4.1.4.
Yes, CVE-2010-3323 can be exploited remotely by attackers to hijack sessions.
The primary attack vector for CVE-2010-3323 involves manipulating the SPLUNKD_SESSION_KEY parameter.