# CVE-2012-4737: Auth bypass in n/a

> Remote authenticated users can bypass outbound-call restrictions in Asterisk by leveraging peer credentials due to missing ACL enforcement.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **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-4737, GHSA-5hf4-mrr5-f9rh

## What is CVE-2012-4737?

CVE-2012-4737 is a medium-severity authentication bypass vulnerability in Digium Asterisk, published on 31 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

channels/chan_iax2.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-cert7, Asterisk Digiumphones 10.x.x-digiumphones before 10.7.1-digiumphones, and Asterisk Business Edition C.3.x before C.3.7.6 does not enforce ACL rules during certain uses of peer credentials, which allows remote authenticated users to bypass intended outbound-call restrictions by leveraging the availability of these credentials.

Weakness: CWE-264

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

It affects 2 products.


Products: Digium Asterisk, Digium Certified Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2012-4737 being exploited?

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

## Other vulnerabilities in Digium Asterisk

- [CVE-2017-14100](https://insights.sbomify.com/CVE-2017-14100/): Command injection in n/a (critical 9.8)
- [CVE-2014-8418](https://insights.sbomify.com/CVE-2014-8418/): Privilege escalation in n/a (critical 9.0)
- [CVE-2011-1599](https://insights.sbomify.com/CVE-2011-1599/): Missing authorization in n/a (critical 9.0)
- [CVE-2017-16671](https://insights.sbomify.com/CVE-2017-16671/): Memory corruption in n/a (high 8.8)
- [CVE-2017-7617](https://insights.sbomify.com/CVE-2017-7617/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4737 is a medium-severity authentication bypass vulnerability in Digium Asterisk, 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-4737 in the wild and no public exploit code.

Affected product: Digium Asterisk. 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-4737/ (Markdown: https://insights.sbomify.com/CVE-2012-4737/index.md)
```

## Sources

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

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