dbcve.org
AsteriskApplication · Digium

CVE-2017-14100

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-02
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
In Asterisk 11.x before 11.25.2, 13.x before 13.17.1, and 14.x before 14.6.1 and Certified Asterisk 11.x before 11.6-cert17 and 13.x before 13.13-cert5, unauthorized command execution is possible. The app_minivm module has an "externnotify" program configuration option that is executed by the MinivmNotify dialplan application. The application uses the caller-id name and number as part of a built string passed to the OS shell for interpretation and execution. Since the caller-id name and number can come from an untrusted source, a crafted caller-id name or number allows an arbitrary shell command injection.

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
How this class of weakness works · CWE-78

User input reaches a shell or system command without being fully separated from the command itself, so an attacker can append their own instructions. Because these run with the application's privileges, it often means full control of the host. The lasting fix is to avoid the shell entirely — call APIs directly and pass arguments as data, never as concatenated strings.

General guidance for the os command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
AsteriskApplication
Affected:= 13.0.0= 13.0.1= 13.0.2= 13.1.0= 13.1.1= 13.2.0= 13.2.1= 13.3.0= 13.3.2= 13.4.0= 13.5.0= 13.6.0
Certified AsteriskApplication
Affected:= 11.6= 13.13

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
Patch available Apply the vendor patch
Vendor patch bugs.debian.org →
Recommended fix High confidence

Asterisk 13.x to 13.17.1 or later; Certified Asterisk 11.6 to 11.6-cert17; Certified Asterisk 13.13 to 13.13-cert5

  1. 1. Identify if the app_minivm module is loaded and in use by checking modules.conf or running 'module show' in the Asterisk CLI.
  2. 2. If app_minivm is loaded and the 'externnotify' configuration option is set in minvm.conf, note that this setting allows command injection via caller-id name/number.
  3. 3. Upgrade Asterisk 13.x to version 13.17.1 or later (such as 13.18.x or latest 13.x stable).
  4. 4. If using Certified Asterisk 11.6, upgrade to version 11.6-cert17 or later.
  5. 5. If using Certified Asterisk 13.13, upgrade to version 13.13-cert5 or later.
  6. 6. After upgrading, verify the externnotify setting in minvm.conf does not use untrusted caller-id data directly in shell commands.
  7. 7. Restart Asterisk services to apply the update.
  8. 8. Test that the MinivmNotify dialplan application still functions correctly with the new version.
Caveat Minor: Ensure any custom externnotify scripts still function correctly after upgrade, as behavior should remain compatible

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

We can apply and verify the patch for your build — typical engagement from $3,550. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14100 — 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-2017-14100 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