CVE-2012-4737
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedchannels/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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe IAX2 channel driver (channels/chan_iax2.c) in Asterisk fails to enforce ACL rules during certain operations using peer credentials. This allows authenticated remote users who possess valid peer credentials to bypass configured outbound-call restrictions, potentially placing unauthorized calls at the expense of the organization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.8.0= 1.8.1= 1.8.1.1= 1.8.1.2= 1.8.2= 1.8.2.1= 1.8.2.2= 1.8.2.3= 1.8.2.4= 1.8.3= 1.8.3.1= 1.8.3.2= 1.8.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Asterisk versionRun `asterisk -V` or `asterisk -vv` from command line, or enter Asterisk CLI and run `core show version`Affected if The installed version matches 1.8.0 through 1.8.3.2, or is 1.8.11 certified version, as listed in affected versions
-
Verify IAX2 module is loadedEnter Asterisk CLI and run `module show like iax` or `iax2 show version`Affected if The IAX2 channel driver module (chan_iax2) is loaded and active
-
Confirm IAX2 peers existEnter Asterisk CLI and run `iax2 show peers` or inspect the IAX configuration file (typically /etc/asterisk/iax.conf) for peer definitionsAffected if One or more IAX2 peers are configured with valid credentials
-
Check for ACL rules on IAX2Inspect /etc/asterisk/iax.conf for `deny` and `permit` directives within peer definitions, or run `iax2 show peer <peername>` in CLI to view ACL settingsAffected if ACL rules (deny/permit) are defined but were being bypassed due to this vulnerability
You are affected if you run an affected Asterisk version (1.8.0-1.8.3.2 or certified 1.8.11) with IAX2 peers configured, particularly if those peers rely on ACLs to restrict outbound calls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Asterisk to version 1.8.15.1/10.7.1 or the corresponding certified/Business Edition fixed versions. Additionally, review and harden ACL configurations around IAX2 peers and consider rotating compromised credentials.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4737 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-4737 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data