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

> Remote authenticated users with originate privileges can execute arbitrary commands via the AMI Originate action in Asterisk.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2186, GHSA-27ch-ccxg-45pf

## What is CVE-2012-2186?

CVE-2012-2186 is a critical command injection vulnerability in n/a, published on 31 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incomplete blacklist vulnerability in main/manager.c in Asterisk Open Source 1.8.x before 1.8.15.1 and 10.x before 10.7.1, Certified Asterisk 1.8.11 before 1.8.11-cert6, Asterisk Digiumphones 10.x.x-digiumphones before 10.7.1-digiumphones, and Asterisk Business Edition C.3.x before C.3.7.6 allows remote authenticated users to execute arbitrary commands by leveraging originate privileges and providing an ExternalIVR value in an AMI Originate action.

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

It affects 5 products.


Products: Asterisk Business Edition, Asterisk Certified Asterisk, Asterisk Digiumphones, Asterisk Open Source, Sangoma Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2012-2186 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2264](https://insights.sbomify.com/CVE-2013-2264/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2186 is a critical command injection vulnerability in n/a, published on 31 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2186 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-2186/ (Markdown: https://insights.sbomify.com/CVE-2012-2186/index.md)
```

## Sources

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

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