# CVE-2009-2946: Code injection in n/a

> Remote attackers can execute arbitrary Perl code in Debian devscripts via crafted pathnames from distribution servers.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2009
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2009-2946, DSA-1878-1, DSA-1878-2, GHSA-9gf3-j9w5-g3hm

## What is CVE-2009-2946?

CVE-2009-2946 is a critical code injection vulnerability in n/a, published on 4 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Eval injection vulnerability in scripts/uscan.pl before Rev 1984 in devscripts allows remote attackers to execute arbitrary Perl code via crafted pathnames on distribution servers for upstream source code used in Debian GNU/Linux packages.

## Which versions are affected by CVE-2009-2946?

It affects 1 product.


Products: Devscripts Devel Team Devscripts.

## How do I fix CVE-2009-2946?

Upgrade to a fixed version.

## Is CVE-2009-2946 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0210](https://insights.sbomify.com/CVE-2012-0210/): Command injection in n/a (critical 9.3)
- [CVE-2012-0211](https://insights.sbomify.com/CVE-2012-0211/): Command injection in n/a (critical 9.3)
- [CVE-2012-0212](https://insights.sbomify.com/CVE-2012-0212/): Command injection in n/a (critical 9.3)
- [CVE-2015-5704](https://insights.sbomify.com/CVE-2015-5704/): Command injection in n/a (high 7.8)
- [CVE-2015-5705](https://insights.sbomify.com/CVE-2015-5705/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2946 and fix it if it is affected.

What it is: CVE-2009-2946 is a critical code injection vulnerability in n/a, published on 4 Sep 2009. 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-2009-2946 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-2009-2946/ (Markdown: https://insights.sbomify.com/CVE-2009-2946/index.md)
```

## Sources

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

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