CVE-2007-4455
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 · uneditedThe SIP channel driver (chan_sip) in Asterisk Open Source 1.4.x before 1.4.11, AsteriskNOW before beta7, Asterisk Appliance Developer Kit 0.x before 0.8.0, and s800i (Asterisk Appliance) 1.x before 1.0.3 allows remote attackers to cause a denial of service (memory exhaustion) via a SIP dialog that causes a large number of history entries to be created.
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 · moderate confidenceThe SIP channel driver (chan_sip) in Asterisk versions 1.4.x before 1.4.11, AsteriskNOW before beta7, and related asterisk appliance products fails to properly limit the number of history entries created during SIP dialogs. Remote attackers can exploit this by initiating SIP dialogs that generate excessive history entries, causing memory exhaustion and a denial of service condition.
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.9<= 0.7<= beta_6CVSS 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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Check if Asterisk is installedRun `asterisk -V` or `asterisk --version` to display the installed Asterisk versionAffected if The version displayed is 1.4.9 or earlier, or the installation is AsteriskNOW beta_6 or earlier, or Asterisk Appliance Developer Kit 0.7 or earlier
-
Verify the SIP channel driver is loadedRun `module show like chan_sip` or `sip show settings` to confirm the chan_sip module is loaded and activeAffected if The SIP channel driver (chan_sip) is loaded and running
-
Confirm SIP peers or users are configuredRun `sip show peers` or `sip show users` to list configured SIP endpointsAffected if There are active SIP peers or users configured, meaning the system is accepting SIP dialogs
-
Check for SIP dialog history configurationReview the sip.conf configuration file for any existing history or debug settings related to dialog trackingAffected if Dialog history tracking is enabled or no rate limiting is configured for SIP dialogs
The system is affected if Asterisk version 1.4.9 or earlier, AsteriskNOW beta_6 or earlier, or Asterisk Appliance Developer Kit 0.7 or earlier is installed with the SIP channel driver active and processing SIP dialogs.
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.11 or later, AsteriskNOW to beta7 or later, or the applicable patched version of the Asterisk Appliance products. As a workaround, consider implementing SIP connection rate limiting at the network perimeter or firewall to reduce exposure to attack.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4455 — 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-4455 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