CVE-2009-2726

N/A
Published: August 12, 2009 at 10:00 AM UTC
Updated: June 16, 2026 at 11:10 PM UTC
3 products affected across 1 vendorAsteriskS800I FirmwareS800I

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 7%

Description

The SIP channel driver in Asterisk Open Source 1.2.x before 1.2.34, 1.4.x before 1.4.26.1, 1.6.0.x before 1.6.0.12, and 1.6.1.x before 1.6.1.4; Asterisk Business Edition A.x.x, B.x.x before B.2.5.9, C.2.x before C.2.4.1, and C.3.x before C.3.1; and Asterisk Appliance s800i 1.2.x before 1.3.0.3 does not use a maximum width when invoking sscanf style functions, which allows remote attackers to cause a denial of service (stack memory consumption) via SIP packets containing large sequences of ASCII decimal characters, as demonstrated via vectors related to (1) the CSeq value in a SIP header, (2) large Content-Length value, and (3) SDP.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < b.2.5.91.2.0 ≤ v < 1.2.341.4.0 ≤ v < 1.4.26.11.6.0 ≤ v < 1.6.0.121.6.1 ≤ v < 1.6.1.4c.2.0 ≤ v ≤ c.2.4.1c.3.0 ≤ v < c.3.1
Affected range stops below 1.2.34, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.4.26.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.6.0.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.6.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below b.2.5.9, so it looks safe — our inference, not a vendor statement
Affected range stops below c.3.1, so it looks safe — our inference, not a vendor statement
1.2.0 ≤ v < 1.3.0.3
Affected range stops below 1.3.0.3, so it looks safe — our inference, not a vendor statement
digium-s800i (same device)
All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (7)

Third Party Advisoryx_refsource_SECUNIABroken LinkVendor Advisory
http://secunia.com/advisories/36227
Mailing Listx_refsource_BUGTRAQBroken LinkThird Party AdvisoryVDB Entry
http://www.securityfocus.com/archive/1/505669/100/0/threaded
VDB Entryx_refsource_BIDBroken LinkExploitThird Party Advisory
http://www.securityfocus.com/bid/36015
VDB Entryx_refsource_SECTRACKBroken LinkThird Party Advisory
http://www.securitytracker.com/id?1022705
VDB Entryx_refsource_VUPENBroken LinkVendor Advisory
http://www.vupen.com/english/advisories/2009/2229

CVSS

Confidentiality
NONE
Integrity
NONE
Availability
COMPLETE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card