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

> Remote attackers with root access to clients can execute arbitrary commands on the server via shell metacharacters in the UUID field.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2503-1, GHSA-pg2p-q27f-4f79

## What is CVE-2012-3366?

CVE-2012-3366 is a critical command injection vulnerability in n/a, published on 3 Jul 2012. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Trigger plugin in bcfg2 1.2.x before 1.2.3 allows remote attackers with root access to the client to execute arbitrary commands via shell metacharacters in the UUID field to the server process (bcfg2-server).

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Anl Bcfg2.

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

Upgrade to a fixed version.

## Is CVE-2012-3366 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3366 is a critical command injection vulnerability in n/a, published on 3 Jul 2012. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3366 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-3366/ (Markdown: https://insights.sbomify.com/CVE-2012-3366/index.md)
```

## Sources

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

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