CVE-2014-8415
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 · uneditedRace condition in the chan_pjsip channel driver in Asterisk Open Source 12.x before 12.7.1 and 13.x before 13.0.1 allows remote attackers to cause a denial of service (assertion failure and crash) via a cancel request for a SIP session with a queued action to (1) answer a session or (2) send ringing.
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 confidenceA race condition exists in the chan_pjsip channel driver of Asterisk where a remote attacker can send a CANCEL request for a SIP session that has a queued action to either answer the session or send ringing, triggering an assertion failure and crash.
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>= 12.0.0, < 12.7.1>= 13.0.0, < 13.0.1CVSS 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.
-
Verify Asterisk is installedRun 'asterisk -V' or 'asterisk --version' to display the installed Asterisk versionAffected if No Asterisk binary is found or the version command fails
-
Confirm the version falls within vulnerable rangeCompare your installed Asterisk version against the affected ranges: 12.0.0 through 12.7.0 for the 12.x branch, or 13.0.0 for the 13.x branchAffected if The installed version is 12.0.0 to 12.7.0 inclusive, or exactly 13.0.0
-
Identify the active SIP channel driverCheck for the presence of pjsip.conf configuration file in /etc/asterisk/ or examine your sip.conf for 'transport=pjsip' references; also check 'module show like pjsip' from Asterisk CLIAffected if The chan_pjsip module is loaded and pjsip is configured as the SIP transport
-
Confirm SIP service is exposedCheck if port 5060 (or custom SIP port) is listening with 'netstat -tulpn | grep sip' or 'ss -tulpn | grep 5060'; verify the system accepts remote SIP trafficAffected if Asterisk is listening on a UDP/TCP SIP port and is reachable from network
You are affected if Asterisk version is 12.0.0-12.7.0 or 13.0.0, chan_pjsip is loaded, and the system accepts SIP traffic that could receive a CANCEL request for an in-progress session.
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 data12.7.113.0.1
Upgrade Asterisk to version 12.7.1 or later for the 12.x branch, or 13.0.1 or later for the 13.x branch to receive the patch that fixes this race condition.
- Consultation3.0 h
- Implementation6.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 $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8415 — 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-2014-8415 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