# CVE-2024-27629: Command injection in n/a

> A local attacker can execute arbitrary code in dc2niix due to improper escaping of generated file names in system calls during compression.

- **Severity:** High 7.8 (`CVSS:3.1/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:** Yes
- **Published:** 28 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-27629, GHSA-25g3-v2pj-968v, UBUNTU-CVE-2024-27629

## What is CVE-2024-27629?

CVE-2024-27629 is a high-severity command injection vulnerability in n/a, published on 28 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in dc2niix before v.1.0.20240202 allows a local attacker to execute arbitrary code via the generated file name is not properly escaped and injected into a system call when certain types of compression are used.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2024-27629?


## How do I fix CVE-2024-27629?

Upgrade to a fixed version.

## Is CVE-2024-27629 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27629 and fix it if it is affected.

What it is: CVE-2024-27629 is a high-severity command injection vulnerability in n/a, published on 28 Jun 2024. 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-2024-27629 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-2024-27629/ (Markdown: https://insights.sbomify.com/CVE-2024-27629/index.md)
```

## Sources

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

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