CVE-2014-8416
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 · uneditedUse-after-free vulnerability in the PJSIP channel driver in Asterisk Open Source 12.x before 12.7.1 and 13.x before 13.0.1, when using the res_pjsip_refer module, allows remote attackers to cause a denial of service (crash) via an in-dialog INVITE with Replaces message, which triggers the channel to be hung up.
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 confidenceUse-after-free vulnerability in Asterisk's PJSIP channel driver when the res_pjsip_refer module processes an in-dialog INVITE containing a Replaces header. The bug occurs because the channel is hung up but external references to it are not properly cleared, leading to a crash when those stale references are dereferenced.
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.
-
Determine Asterisk versionRun 'asterisk -V' or 'asterisk --version' to get the installed version numberAffected if Version is 12.0.0 through 12.7.0, or 13.0.0 (only version 13.0.0 is affected in the 13.x line)
-
Confirm PJSIP channel driver is in useCheck /etc/asterisk/pjsip.conf exists and contains configured endpoints, or run 'module show like pjsip' to list loaded PJSIP modulesAffected if PJSIP configuration files exist and PJSIP modules are loaded - the SIP chan_pjsip driver must be in use for this vulnerability to apply
-
Verify res_pjsip_refer module is loadedRun 'module show like res_pjsip_refer' in the Asterisk CLI to check if the module is loadedAffected if The res_pjsip_refer module is loaded and active - this module handles the REFER requests and Replays header processing that triggers the flaw
-
Check for recent REFER-based transfers or call transfersReview Asterisk logs (typically /var/log/asterisk/full or /var/log/messages) for INVITE requests containing Replaces headers, or enable SIP debugging with 'pjsip set logger on' to capture real-time trafficAffected if Blind call transfers or attended transfers using the Replaces header are being performed in an active call context
You are affected if you run Asterisk 12.0.0-12.7.0 or 13.0.0 with the PJSIP channel stack enabled and the res_pjsip_refer module loaded while using call transfer features that generate in-dialog INVITE requests with Replaces headers.
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 12.x) or 13.0.1 or later (for 13.x). If immediate upgrade is not feasible, consider disabling the res_pjsip_refer module if blind transfer functionality is not required.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8416 — 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-8416 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