# CVE-2015-4035: Command injection in n/a

> Attackers can execute arbitrary code by tricking users into running xzgrep on a crafted filename containing semicolons.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mf33-8p24-6h53

## What is CVE-2015-4035?

CVE-2015-4035 is a high-severity command injection vulnerability in n/a, published on 25 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

scripts/xzgrep.in in xzgrep 5.2.x before 5.2.0, before 5.0.0 does not properly process file names containing semicolons, which allows remote attackers to execute arbitrary code by having a user run xzgrep on a crafted file name.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-4035?

It affects 1 product.


Products: Tukaani Xz.

## How do I fix CVE-2015-4035?

No fix has been published for CVE-2015-4035 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-4035 being exploited?

There is no known exploitation of CVE-2015-4035 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-3094](https://insights.sbomify.com/CVE-2024-3094/): Xz: malicious code in distributed source (critical 10.0)
- [CVE-2020-22916](https://insights.sbomify.com/CVE-2020-22916/): Denial of service in n/a (medium 5.5)
- [CVE-2026-34743](https://insights.sbomify.com/CVE-2026-34743/): XZ Utils: Buffer overflow in lzma_index_append() (low 1.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4035 and fix it if it is affected.

What it is: CVE-2015-4035 is a high-severity command injection vulnerability in n/a, published on 25 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-4035 in the wild and no public exploit code.

Affected product: n/a. 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-2015-4035/ (Markdown: https://insights.sbomify.com/CVE-2015-4035/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-4035
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-4035
- OSV: https://osv.dev/vulnerability/CVE-2015-4035

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-4035/
Summaries are generated and may contain mistakes; the official description above is the record.