CVE-2010-2502
Summary
| CVE | CVE-2010-2502 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2010-06-28 18:30:00 UTC |
| Updated | 2026-04-29 01:13:23 UTC |
| Description | Multiple directory traversal vulnerabilities in Splunk 4.0 through 4.0.10 and 4.1 through 4.1.1 allow (1) remote attackers to read arbitrary files, aka SPL-31194; (2) remote authenticated users to modify arbitrary files, aka SPL-31063; or (3) have an unknown impact via redirects, aka SPL-31067. |
Risk And Classification
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
MediumAuthentication
SingleConfidentiality
CompleteIntegrity
PartialAvailability
PartialAV:N/AC:M/Au:S/C:C/I:P/A:P
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Splunk | Splunk | 4.0 | All | All | All |
| Application | Splunk | Splunk | 4.0.1 | All | All | All |
| Application | Splunk | Splunk | 4.0.10 | All | All | All |
| Application | Splunk | Splunk | 4.0.2 | All | All | All |
| Application | Splunk | Splunk | 4.0.3 | All | All | All |
| Application | Splunk | Splunk | 4.0.4 | All | All | All |
| Application | Splunk | Splunk | 4.0.5 | All | All | All |
| Application | Splunk | Splunk | 4.0.6 | All | All | All |
| Application | Splunk | Splunk | 4.0.7 | All | All | All |
| Application | Splunk | Splunk | 4.0.8 | All | All | All |
| Application | Splunk | Splunk | 4.0.9 | All | All | All |
| Application | Splunk | Splunk | 4.1 | All | All | All |
| Application | Splunk | Splunk | 4.1.1 | All | All | All |
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Splunk : Splunk Critical Maintenance Release and Patch - May 3rd, 2010 | af854a3a-2127-422b-91ae-364da2661108 | www.splunk.com | Patch, Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.