dbcve.org
Vbond OrchestratorApplication · Cisco

CVE-2018-0348

HIGH · 7.2 CVSS v3.1 Published 2018-07-18
Fix available
A fix is available. Upgrade to 18.3.0 or later.
See remediation →
78/100
Remediation priority · High
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
A vulnerability in the CLI of the Cisco SD-WAN Solution could allow an authenticated, remote 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 malicious input to the load command within the VPN subsystem. The attacker must be authenticated to access the affected CLI parameter. A successful exploit could allow an attacker to execute commands with root privileges. This vulnerability affects the following Cisco products if they are running a release of the Cisco SD-WAN Solution prior to Release 18.3.0: vBond Orchestrator Software, vEdge 100 Series Routers, vEdge 1000 Series Routers, vEdge 2000 Series Routers, vEdge 5000 Series Routers, vEdge Cloud Router Platform, vManage Network Management Software, vSmart Controller Software. Cisco Bug IDs: CSCvi69866.

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

Command injection vulnerability in Cisco SD-WAN CLI where insufficient input validation on the 'load' command within the VPN subsystem allows an authenticated attacker to inject and execute arbitrary commands with root privileges. The vulnerability affects vBond Orchestrator, vEdge routers (100/1000/2000/5000 series), vEdge Cloud Router, vManage, and vSmart Controller Software when running releases prior to 18.3.0.

MitigationUpgrade to Cisco SD-WAN Release 18.3.0 or later. Prior to upgrade, enforce least-privilege access to CLI and monitor for unauthorized authentication attempts.

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
Vbond OrchestratorApplication
Affected:all versions
Vedge PlusWeb browser
Affected:all versions
Vedge ProWeb browser
Affected:all versions
Vmanage Network ManagementApplication
Affected:all versions
Vsmart ControllerApplication
Affected:all versions
Vedge 100 FirmwareOperating system
Affected:< 18.3.0
Vedge 100b FirmwareOperating system
Affected:< 18.3.0
Vedge 100m FirmwareOperating system
Affected:< 18.3.0

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

CVSS:3.1/AV:N/AC:L/PR:H/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 installed Cisco SD-WAN product and version
    Run 'show version' or 'show system information' in the CLI to determine the exact software version and product type (vBond, vEdge, vManage, vSmart)
    Affected if The product is any of the affected Cisco SD-WAN components and the version is prior to 18.3.0 or is an 'all versions' product
  2. Verify the VPN subsystem is configured
    Check if the VPN subsystem is active by running 'show vpn' or 'show configuration vpn' in the CLI
    Affected if VPN subsystem is configured and accessible to the authenticated user
  3. Confirm 'load' command availability in VPN context
    Enter VPN configuration mode (using 'vpn <id>' command) and check if 'load' command is available by running '?' or 'load ?'
    Affected if The 'load' command is present and accepts user input for configuration file loading
  4. Review authentication and CLI access logs
    Check system logs for any 'load' command executions and look for unexpected command sequences. Run 'show logs' or check /var/log directory for authentication events
    Affected if There are log entries showing 'load' command usage with suspicious parameters or unexpected command injection patterns
  5. Check for unexpected root-level processes or files
    Run 'show processes' and 'show files' commands to look for any unauthorized processes or configuration files that may indicate command injection exploitation
    Affected if Unexpected processes are running or unknown files exist in the system directories

The environment is affected if any Cisco SD-WAN product (vBond, vEdge, vManage, vSmart) is running a version prior to 18.3.0 and the VPN subsystem with the 'load' command is accessible to authenticated users.

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 18.3.0 or later
Fixed in 18.3.0
Interim mitigation

Upgrade to Cisco SD-WAN Release 18.3.0 or later. Prior to upgrade, enforce least-privilege access to CLI and monitor for unauthorized authentication attempts.

Fix this in Vbond Orchestrator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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