CVE-2012-5976
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 · uneditedMultiple stack consumption vulnerabilities in Asterisk Open Source 1.8.x before 1.8.19.1, 10.x before 10.11.1, and 11.x before 11.1.2; Certified Asterisk 1.8.11 before 1.8.11-cert10; and Asterisk Digiumphones 10.x-digiumphones before 10.11.1-digiumphones allow remote attackers to cause a denial of service (daemon crash) via TCP data using the (1) SIP, (2) HTTP, or (3) XMPP protocol.
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 confidenceStack consumption vulnerability in Asterisk allows remote attackers to cause denial of service (daemon crash) via specially crafted TCP data using SIP, HTTP, or XMPP protocols.
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.19.0= 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.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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Check installed Asterisk versionRun `asterisk -V` or `asterisk --version` from command line, or enter Asterisk CLI and run `core show version`Affected if Version is 1.8.19.0 or earlier, or is Digium Certified Asterisk 1.8.11
-
Verify SIP over TCP is enabledIn Asterisk CLI, run `sip show settings` and look for the 'TCP' setting under 'SIP General Settings'. Alternatively check sip.conf for `tcpenable=yes`Affected if SIP TCP support is enabled and Asterisk version is vulnerable
-
Confirm HTTP server is enabledIn Asterisk CLI, run `http show status`. Alternatively check http.conf for `enabled=yes` and `bindaddr` settingsAffected if HTTP server is enabled and Asterisk version is vulnerable
-
Check if XMPP module is loadedIn Asterisk CLI, run `module show like xmpp` to see if any XMPP modules are loaded. Check xmpp.conf for configured XMPP clientsAffected if XMPP support is enabled/loaded and Asterisk version is vulnerable
-
Determine network exposure of vulnerable servicesReview firewall rules and Asterisk bind address settings for SIP (UDP/TCP ports 5060/5061), HTTP (port 8088/8089), and XMPP ports to see if the service is reachable from untrusted networksAffected if Any of SIP TCP, HTTP, or XMPP services are exposed to untrusted networks and Asterisk version is vulnerable
You are affected if Asterisk version is 1.8.19.0 or earlier (or Digium Certified 1.8.11) AND at least one of SIP over TCP, HTTP server, or XMPP is enabled and reachable from the network.
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.19.1/10.11.1/11.1.2 or later (or corresponding certified/digiumphone versions) to patch the vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5976 — 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-5976 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