# CVE-2023-27635: Command injection in n/a

> Attackers can execute arbitrary shell commands via crafted .deb files in debian-goodies, requiring user interaction to view the path.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Mar 2023
- **Updated:** 6 Mar 2025
- **Also known as:** DEBIAN-CVE-2023-27635, GHSA-45q8-6w7r-v56h, UBUNTU-CVE-2023-27635, USN-6714-1

## What is CVE-2023-27635?

CVE-2023-27635 is a high-severity command injection vulnerability in n/a, published on 5 Mar 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

debmany in debian-goodies 0.88.1 allows attackers to execute arbitrary shell commands (because of an eval call) via a crafted .deb file. (The path is shown to the user before execution.)

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2023-27635?

It affects 1 product.


Products: Debian Debmany.

## How do I fix CVE-2023-27635?

Apply the vendor's patch.

## Is CVE-2023-27635 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27635 and fix it if it is affected.

What it is: CVE-2023-27635 is a high-severity command injection vulnerability in n/a, published on 5 Mar 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-27635 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-2023-27635/ (Markdown: https://insights.sbomify.com/CVE-2023-27635/index.md)
```

## Sources

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

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