Ios XeApplication · Cisco

CVE-2019-16011

HIGH · 7.8 CVSS v3.1 Published 2020-04-29
Fix available
A fix is available. Upgrade to 17.2.1r or later.
See remediation →
80/100
Remediation priority · High
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
A vulnerability in the CLI of Cisco IOS XE SD-WAN Software could allow an authenticated, local attacker to inject arbitrary commands that are executed with root privileges. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by authenticating to the device and submitting crafted input to the CLI utility. The attacker must be authenticated to access the CLI utility. A successful exploit could allow the attacker to execute commands with root privileges.

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

A command injection vulnerability in the Cisco IOS XE SD-WAN Software CLI allows authenticated local attackers to inject arbitrary commands that execute with root privileges due to insufficient input validation in the CLI utility.

MitigationApply the vendor patch from Cisco to address the input validation vulnerability in IOS XE SD-WAN, and restrict CLI access to trusted administrators until the patch is deployed.

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
Ios XeApplication
Affected:= 16.10.2= 16.11>= 16.12, < 17.2.1r= 16.9= 16.10= 17.3

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

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

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. Identify the IOS XE version
    Run 'show version' or 'show version | include IOS XE' command in the CLI to display the installed software version
    Affected if The version shown matches one of the affected versions: 16.9, 16.10, 16.10.2, 16.11, 16.12 through 17.2.1r (excluding 17.2.1r), or 17.3
  2. Verify SD-WAN feature is enabled
    Run 'show sdwan version' or check the configuration for SD-WAN related commands such as 'sdwan', 'vsmart', 'vedge' in the running configuration using 'show run | include sdwan'
    Affected if SD-WAN commands are present or the SD-WAN feature is active on the device
  3. Confirm CLI access method
    Check if local CLI authentication is configured. Use 'show running-config | include username' to verify local user accounts exist, or check for VTY/TTY access lines with 'show line'
    Affected if Local CLI authentication is enabled, allowing authenticated users to access the command interface
  4. Check for privilege escalation indicators
    Review recent command history or logs for unexpected commands executed as root. Use 'show logging | include exec' or check authpriv logs for privilege changes
    Affected if Any unexpected or unauthorized commands appear in logs or command history with elevated privileges

The environment is affected if the device runs a vulnerable IOS XE version (16.9, 16.10, 16.10.2, 16.11, 16.12-17.2.1, or 17.3) AND has SD-WAN functionality enabled, allowing an authenticated local attacker to inject commands through the SD-WAN CLI.

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.

From vendor data
Upgrade available Upgrade to 17.2.1r or later
Fixed in 17.2.1r
Interim mitigation

Apply the vendor patch from Cisco to address the input validation vulnerability in IOS XE SD-WAN, and restrict CLI access to trusted administrators until the patch is deployed.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-16011 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-16011 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