CVE-2007-5358 json
Multiple buffer overflows in the voicemail functionality in Asterisk 1.4.x before 1.4.13, when using IMAP storage, might allow (1) remote a…
published 2007-10-12 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-5336
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.9%
- EPSS 3.9% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Multiple buffer overflows in the voicemail functionality in Asterisk 1.4.x before 1.4.13, when using IMAP storage, might allow (1) remote attackers to execute arbitrary code via a long combination of Content-type and Content-description headers, or (2) local users to execute arbitrary code via a long combination of astspooldir, voicemail context, and voicemail mailbox fields. NOTE: vector 2 requires write access to Asterisk configuration files.
Patch / fix
- asterisk Debian 14 1:1.4.13~dfsg-1
debian advisories DEBIAN-CVE-2007-5358
Exploit prediction
3.86% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
- downloads.digium.com /pub/security/AST-2007-022.html
-
osvdb.org
/38201
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/37052
vdb-entry
-
osvdb.org
/38202
vdb-entry
-
secunia.com
/advisories/27184
third-party-advisory
-
securitytracker.com
/id?1018804
vdb-entry
-
securityfocus.com
/bid/26005
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/37051
vdb-entry
-
securityfocus.com
/archive/1/481996/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2007/3454
vdb-entry
Sources
- CVE List CVE-2007-5358
- NVD CVE-2007-5358
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.