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

> Remote attackers can execute arbitrary commands on systems using ConnMan by sending malicious DHCP replies containing shell metacharacters.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 18 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2321, GHSA-frmw-wwv7-8q6q

## What is CVE-2012-2321?

CVE-2012-2321 is a critical command injection vulnerability in n/a, published on 18 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The loopback plug-in in ConnMan before 0.85 allows remote attackers to execute arbitrary commands via shell metacharacters in the (1) host name or (2) domain name in a DHCP reply.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Connman Connman.

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

Upgrade to a fixed version.

## Is CVE-2012-2321 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2320](https://insights.sbomify.com/CVE-2012-2320/): Security feature bypass in n/a (high 7.8)
- [CVE-2012-2322](https://insights.sbomify.com/CVE-2012-2322/): Integer overflow in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2321 is a critical command injection vulnerability in n/a, published on 18 May 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-2321 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-2321/ (Markdown: https://insights.sbomify.com/CVE-2012-2321/index.md)
```

## Sources

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

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