Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2011-2529: chan_sip.c in the SIP channel driver in Asterisk Open Source 1.6.x before 1.6.2.18.1 and 1.8.x before 1.8.4.3 does not properly handle '\0'…

MediumCVSS 5.0 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 4.2% (FIRST EPSS); higher than 91.2% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: asterisk (Debian:14) 1:1.8.4.3-1; asterisk (Debian:5.0) 1:1.4.21.2~dfsg-3+lenny3; asterisk (Debian:6.0) 1:1.6.2.9-2+squeeze3.

Low priority for now. Upgrade to asterisk (Debian:14) 1:1.8.4.3-1; asterisk (Debian:5.0) 1:1.4.21.2~dfsg-3+lenny3; asterisk (Debian:6.0) 1:1.6.2.9-2+squeeze3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

chan_sip.c in the SIP channel driver in Asterisk Open Source 1.6.x before 1.6.2.18.1 and 1.8.x before 1.8.4.3 does not properly handle '\0' characters in SIP packets, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted packet.

Published
Jul 6, 2011
Updated
Jun 16, 2026
EPSS
4.2% · 91th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2011-2529

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for digium records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
digiumasterisk

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • digium asterisk1.6.0
  • digium asterisk1.6.0.1
  • digium asterisk1.6.0.10
  • digium asterisk1.6.0.11
  • digium asterisk1.6.0.12
  • digium asterisk1.6.0.13
  • digium asterisk1.6.0.14
  • digium asterisk1.6.0.15
+12 more rows
  • digium asterisk1.6.0.16
  • digium asterisk1.6.0.17
  • digium asterisk1.6.0.18
  • digium asterisk1.6.0.19
  • digium asterisk1.6.0.2
  • digium asterisk1.6.0.20
  • digium asterisk1.6.0.21
  • digium asterisk1.6.0.22
  • digium asterisk1.6.0.23
  • digium asterisk1.6.0.24
  • digium asterisk1.6.0.25
  • digium asterisk1.6.0.26

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:14asteriskbefore 1:1.8.4.3-11:1.8.4.3-1
Debian:5.0asteriskbefore 1:1.4.21.2~dfsg-3+lenny31:1.4.21.2~dfsg-3+lenny3
Debian:6.0asteriskbefore 1:1.6.2.9-2+squeeze31:1.6.2.9-2+squeeze3

Same product

digium: all records

Other highest-scoring records for the same primary product.

  • CVE-2006-5444Integer overflow in the get_input function in the Skinny channel driver (chan_skinny.c) in Asterisk 1.0.x before 1.0.12 and 1.2.x before…
    56Plan
  • CVE-2017-17850An issue was discovered in Asterisk 13.18.4 and older, 14.7.4 and older, 15.1.4 and older, and 13.18-cert1 and older.
    53Plan
  • CVE-2019-18610An issue was discovered in manager.c in Sangoma Asterisk through 13.x, 16.x, 17.x and Certified Asterisk 13.21 through 13.21-cert4.
    50Plan

Published before and after this one in the same product

  • ← EarlierCVE-2011-1599Apr 26, 2011 · manager.c in the Manager Interface in Asterisk Open Source 1.4.x before 1.4.40.1, 1.6.1.x before 1.6.1.25, 1.6.2.x before 1.6.2.17.3, and 1.
    37Monitor
  • ← EarlierCVE-2011-2216Jun 6, 2011 · reqresp_parser.c in the SIP channel driver in Asterisk Open Source 1.8.x before 1.8.4.2 does not initialize certain strings, which allows…
    21Monitor
  • Later →CVE-2011-2535Jul 6, 2011 · 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…
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:asterisk1:1.8.4.3-1 · Debian:14Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
None
Integrity impact
None
Availability impact
P

Weakness class (CWE)

CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

CVSS vector

AV:N/AC:L/Au:N/C:N/I:N/A:P

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records