CVE-2008-2119 json
Asterisk Open Source 1.0.x and 1.2.x before 1.2.29 and Business Edition A.x.x and B.x.x before B.2.5.3, when pedantic parsing (aka pedantic…
published 2008-06-04 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2116
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.3%
- EPSS 7.3% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Asterisk Open Source 1.0.x and 1.2.x before 1.2.29 and Business Edition A.x.x and B.x.x before B.2.5.3, when pedantic parsing (aka pedanticsipchecking) is enabled, allows remote attackers to cause a denial of service (daemon crash) via a SIP INVITE message that lacks a From header, related to invocations of the ast_uri_decode function, and improper handling of (1) an empty const string and (2) a NULL pointer.
Patch / fix
- asterisk Debian 14 1.4
debian advisories DEBIAN-CVE-2008-2119
Timeline
- Published
- First public exploit (EDB-5749)
Exploit prediction
7.27% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-5749 Asterisk 1.2.x - SIP channel driver / in pedantic mode Remote Crash dos, 2008-06-05
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
exploit-db.com
/exploits/5749
exploit
-
security.gentoo.org
/glsa/glsa-200905-01.xml
vendor-advisory
-
secunia.com
/advisories/30517
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/42823
vdb-entry
- bugs.digium.com /view.php?id=12607
-
securitytracker.com
/id?1020166
vdb-entry
-
securityfocus.com
/archive/1/493020/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2008/1731
vdb-entry
-
secunia.com
/advisories/34982
third-party-advisory
- svn.digium.com /view/asterisk?view=rev&revision=120109
- downloads.digium.com /pub/security/AST-2008-008.html
Sources
- CVE List CVE-2008-2119
- NVD CVE-2008-2119
Fencer Vulns 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.