CVE-2011-2535 json
chan_iax2.c in the IAX2 channel driver in Asterisk Open Source 1.4.x before 1.4.41.1, 1.6.2.x before 1.6.2.18.1, and 1.8.x before 1.8.4.3,…
published 2011-07-06 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2518
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
chan_iax2.c in the IAX2 channel driver in Asterisk Open Source 1.4.x before 1.4.41.1, 1.6.2.x before 1.6.2.18.1, and 1.8.x before 1.8.4.3, and Asterisk Business Edition C.3 before C.3.7.3, accesses a memory address contained in an option control frame, which allows remote attackers to cause a denial of service (daemon crash) or possibly have unspecified other impact via a crafted frame.
Patch / fix
- asterisk Debian 14 1:1.8.4.3-1
debian advisories DEBIAN-CVE-2011-2535
Exploit prediction
4.61% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
downloads.asterisk.org
/pub/security/AST-2011-010-1.8.diff
patch
-
debian.org
/security/2011/dsa-2276
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2011-July/062628.html
vendor-advisory
-
secunia.com
/advisories/44973
third-party-advisory, vendor-advisory
-
downloads.asterisk.org
/pub/security/AST-2011-010.html
vendor-advisory
-
secunia.com
/advisories/45048
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/68205
vdb-entry
-
securityfocus.com
/bid/48431
vdb-entry
-
securitytracker.com
/id?1025708
vdb-entry
-
secunia.com
/advisories/45239
third-party-advisory
-
osvdb.org
/73309
vdb-entry
-
secunia.com
/advisories/45201
third-party-advisory
Sources
- CVE List CVE-2011-2535
- NVD CVE-2011-2535
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.