# CVE-2012-2240: Command injection in n/a

> Remote attackers can execute arbitrary commands via the dscverify.pl script in devscripts, requiring an upgrade to mitigate.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2240, GHSA-cx6j-736h-qcc7

## What is CVE-2012-2240?

CVE-2012-2240 is a high-severity command injection vulnerability in n/a, published on 1 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

scripts/dscverify.pl in devscripts before 2.12.3 allows remote attackers to execute arbitrary commands via unspecified vectors related to "arguments to external commands."

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-2240?

It affects 1 product.


Products: Devscripts Devel Team Devscripts.

## How do I fix CVE-2012-2240?

Upgrade to a fixed version.

## Is CVE-2012-2240 being exploited?

There is no known exploitation of CVE-2012-2240 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-2009-2946](https://insights.sbomify.com/CVE-2009-2946/): Code 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2240 and fix it if it is affected.

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

## Sources

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

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