CVE-2013-6771 Directory traversal vulnerability in the collect script in Splunk before 5.0.5 allows remote attackers to execute arbitrary commands via a ..
Critical 9.3
Published
Updated
Check this codebase for CVE-2013-6771 and fix it if it is affected.
What it is: CVE-2013-6771 is a critical vulnerability in Splunk Splunk, published on 7 Aug 2014.
Exploitation: There is no known exploitation of CVE-2013-6771 in the wild and no public exploit code.
Affected product: Splunk Splunk. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2013-6771/ (Markdown: https://insights.sbomify.com/CVE-2013-6771/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2013-6771?
CVE-2013-6771 is a critical vulnerability in Splunk Splunk, published on 7 Aug 2014.
Official description
Directory traversal vulnerability in the collect script in Splunk before 5.0.5 allows remote attackers to execute arbitrary commands via a .. (dot dot) in the file parameter. NOTE: this issue was SPLIT per ADT2 due to different vulnerability types. CVE-2013-7394 is for the issue in the "runshellscript echo.sh" script.
Weakness: CWE-22
Which versions are affected by CVE-2013-6771?
It affects 1 product.
Products include Splunk Splunk.
How do I fix CVE-2013-6771?
No fix has been published for CVE-2013-6771 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-6771 being exploited?
There is no known exploitation of CVE-2013-6771 in the wild and no public exploit code.
Other vulnerabilities in Splunk Splunk
- CVE-2026-20253 Splunk Enterprise Missing Authentication for Critical Function
- CVE-2026-76268 Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise
- CVE-2026-76284 Improper Neutralization in Splunk Enterprise
- CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise
- CVE-2017-17067 Auth bypass in n/a
Sources
Also known as GHSA-97v3-fx5j-w6pp.