CVE-2007-5358
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflows in Asterisk 1.4.x voicemail functionality when using IMAP storage allow remote attackers to execute arbitrary code via specially crafted Content-type and Content-description headers, or local users with write access to Asterisk configuration files to execute code via long astspooldir, voicemail context, and voicemail mailbox fields.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.4.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Asterisk versionRun 'asterisk -V' or 'asterisk -x "core show version"' to determine the installed version of AsteriskAffected if The installed version is 1.4.12 or earlier
-
Verify IMAP voicemail storage is in useExamine /etc/asterisk/imap.conf or run 'asterisk -x " voicemail show settings"' to check if IMAP storage is configured for voicemailAffected if IMAP storage is enabled in the voicemail configuration
-
Inspect voicemail configuration files for long field valuesReview /etc/asterisk/voicemail.conf and look for the 'astspooldir', 'context', and 'mailbox' settings; check if any contain unusually long string values that could indicate exploitationAffected if Configuration files contain long values in astspooldir, voicemail context, or mailbox fields, or are writable by untrusted users
-
Check file permissions on Asterisk configuration directoryRun 'ls -la /etc/asterisk/' and verify that configuration files are not world-writable or group-writable by unauthorized usersAffected if Asterisk configuration files are writable by users other than root/asterisk
You are affected if running Asterisk version 1.4.12 or earlier with IMAP voicemail storage enabled, or if Asterisk configuration files are writable by untrusted local users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Asterisk to version 1.4.13 or later which contains the patched bounds checking for the IMAP voicemail storage functionality; if immediate upgrade is not feasible, disable IMAP voicemail storage and restrict access to Asterisk configuration files.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-5358 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data