# CVE-2016-1253: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in LZMA-compressed filenames, affecting Debian systems using the most package.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-1253, DLA-745-1, GHSA-mr5m-5c2f-66xv, UBUNTU-CVE-2016-1253

## What is CVE-2016-1253?

CVE-2016-1253 is a critical command injection vulnerability in n/a, published on 5 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The most package in Debian wheezy before 5.0.0a-2.2, in Debian jessie before 5.0.0a-2.3+deb8u1, and in Debian unstable before 5.0.0a-3 allows remote attackers to execute arbitrary commands via shell metacharacters in the name of an LZMA-compressed file.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2016-1253?

It affects 1 product.


Products: Debian Most.

## How do I fix CVE-2016-1253?

Apply the vendor's patch.

## Is CVE-2016-1253 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1253 and fix it if it is affected.

What it is: CVE-2016-1253 is a critical command injection vulnerability in n/a, published on 5 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1253 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-2016-1253/ (Markdown: https://insights.sbomify.com/CVE-2016-1253/index.md)
```

## Sources

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

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