dbcve.org
Certified AsteriskApplication · Digium

CVE-2014-8418

HIGH · 9.0 CVSS v2.0 Published 2014-11-24
Fix available
A fix is available. Upgrade to 11.14.1 / 12.7.1 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The DB dialplan function in Asterisk Open Source 1.8.x before 1.8.32, 11.x before 11.1.4.1, 12.x before 12.7.1, and 13.x before 13.0.1 and Certified Asterisk 1.8 before 1.8.28-cert8 and 11.6 before 11.6-cert8 allows remote authenticated users to gain privileges via a call from an external protocol, as demonstrated by the AMI protocol.

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 confidence

The DB dialplan function in Asterisk contains a privilege escalation vulnerability where remote authenticated users can gain elevated privileges through calls initiated via external protocols, specifically the Asterisk Management Interface (AMI). This allows an attacker with basic AMI access to execute arbitrary code or manipulate dialplan execution context.

MitigationUpgrade Asterisk to version 1.8.32+, 11.1.4.1+, 12.7.1+, or 13.0.1+ (or corresponding certified versions). If immediate patching is not possible, restrict AMI access to trusted IP addresses and enforce strong authentication for AMI connections.

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
Certified AsteriskApplication
Affected:= 1.8.28= 11.6= 11.6.0
AsteriskApplication
Affected:>= 1.8.0, <= 1.8.32.0>= 11.0.0, < 11.14.1>= 12.0.0, < 12.7.1

CVSS 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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine Asterisk version
    Run 'asterisk -V' or 'core show version' in the Asterisk CLI to get the exact version number
    Affected if The installed version falls within: 1.8.0 to 1.8.32.0, 11.0.0 to 11.14.0, 12.0.0 to 12.7.0, or is 1.8.28, 11.6, or 11.6.0 (certified versions)
  2. Verify AMI is enabled
    Check /etc/asterisk/manager.conf (or equivalent path) for a [general] section with 'enabled = yes' or look for any [username] sections that define AMI users
    Affected if AMI is enabled and accessible, as the vulnerability is exploited through AMI-initiated calls
  3. Check AMI network exposure
    Review manager.conf for the 'bindaddr' setting and any firewall rules or ACLs controlling access to port 5038 (default AMI port)
    Affected if AMI is bound to a non-localhost address or is accessible from untrusted networks
  4. Identify dialplan DB function usage
    Search extensions.conf and related dialplan files for references to 'DB' or 'DB_DELETE', 'DB_GET', 'DB PUT', 'DB_EXISTS' functions which use the DB dialplan functionality
    Affected if The dialplan uses the DB family functions for database operations, allowing an authenticated AMI user to manipulate dialplan context
  5. Review AMI user privileges
    Examine manager.conf for AMI user accounts and their 'read'/'write' permissions, particularly checking for 'system' or 'command' privileges that allow code execution
    Affected if AMI users have elevated privileges or write access that permits issuingOriginate commands or executing system commands

You are affected if your Asterisk version is within the vulnerable ranges AND AMI is enabled and accessible to the attacker, allowing them to trigger dialplan DB function calls with elevated privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 11.14.1 / 12.7.1 or later
Fixed in 11.14.112.7.1
Interim mitigation

Upgrade Asterisk to version 1.8.32+, 11.1.4.1+, 12.7.1+, or 13.0.1+ (or corresponding certified versions). If immediate patching is not possible, restrict AMI access to trusted IP addresses and enforce strong authentication for AMI connections.

Recommended fix High confidence

Asterisk 1.8.32.1+, 11.14.1+, 12.7.1+, or 13.0.1+ (or Certified 1.8.28-cert8+, 11.6-cert8+)

  1. 1. Identify the currently running Asterisk branch (1.8.x, 11.x, 12.x, or 13.x)
  2. 2. For Asterisk 1.8.x: Upgrade to version 1.8.32.1 or later (or 1.8.28-cert8 if using Certified Asterisk)
  3. 3. For Asterisk 11.x: Upgrade to version 11.14.1 or later (or 11.6-cert8 if using Certified Asterisk 11.6)
  4. 4. For Asterisk 12.x: Upgrade to version 12.7.1 or later
  5. 5. For Asterisk 13.x: Upgrade to version 13.0.1 or later
  6. 6. After upgrade, restart the Asterisk service
  7. 7. Verify the DB dialplan function privilege escalation is no longer present
Caveat Minor release upgrades may include feature changes; review release notes for backward compatibility notes on dialplan functions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Certified Asterisk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA2.0 h
19.0 hours of engineering $3,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,184.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8418 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-8418 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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