dbcve.org
Vbond OrchestratorApplication · Cisco

CVE-2018-0349

CRITICAL · 9.8 CVSS v3.1 Published 2018-07-18
Fix available
A fix is available. Upgrade to 18.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Cisco SD-WAN Solution could allow an authenticated, remote attacker to overwrite arbitrary files on the underlying operating system of an affected device. The vulnerability is due to improper input validation of the request admin-tech command in the CLI of the affected software. An attacker could exploit this vulnerability by modifying the request admin-tech command in the CLI of an affected device. A successful exploit could allow the attacker to overwrite arbitrary files on the underlying operating system of an affected device and escalate their privileges to the root user. 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: CSCvi69852, CSCvi69856.

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 SD-WAN CLI allows authenticated attackers to manipulate the 'request admin-tech' command to write arbitrary files to the underlying operating system and escalate privileges to root. The flaw stems from improper input validation in the CLI interface.

MitigationUpgrade all affected Cisco SD-WAN components (vBond, vEdge, vManage, vSmart) to Release 18.3.0 or later. Limit CLI access to trusted administrators only until patching is complete.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Cisco SD-WAN component
    Log into the device and run the appropriate show command (such as 'show version' or 'show hardware') to determine if the system is a vBond Orchestrator, vEdge (Plus/Pro/100/100b/100m), vManage, or vSmart Controller
    Affected if The device is any of the affected product types: vBond Orchestrator, vEdge Plus, vEdge Pro, vManage, vSmart Controller, or vEdge 100/100b/100m
  2. Check the firmware or software version
    Use the CLI to retrieve the installed version number; for vEdge 100/100b/100m devices, compare the firmware version to 18.3.0
    Affected if For vEdge 100/100b/100m: version is lower than 18.3.0; for vBond, vEdge Plus/Pro, vManage, vSmart: all versions are affected since no fixed version is listed
  3. Verify CLI access is enabled
    Confirm that the CLI interface is accessible and that authentication is configured (the vulnerability requires an authenticated attacker to issue the 'request admin-tech' command)
    Affected if CLI access is available to any authenticated user, since the flaw is exploited through the 'request admin-tech' command interface

The environment is affected if the device runs any Cisco SD-WAN component (vBond, vEdge Plus/Pro, vManage, vSmart, or vEdge 100/100b/100m) with a version lower than 18.3.0 for vEdge 100 series, or any version for the other affected products, and CLI access is available.

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

Upgrade all affected Cisco SD-WAN components (vBond, vEdge, vManage, vSmart) to Release 18.3.0 or later. Limit CLI access to trusted administrators only until patching is complete.

Recommended fix High confidence

Cisco SD-WAN Solution Release 18.3.0 or later

  1. 1. Identify the specific Cisco SD-WAN product (vBond Orchestrator, vEdge, vManage, or vSmart Controller) that needs remediation
  2. 2. Download the Cisco SD-WAN Release 18.3.0 or later software from the Cisco Software Download Center (software.cisco.com)
  3. 3. Review the Cisco SD-WAN upgrade documentation for your specific product to understand the upgrade procedure
  4. 4. Create a backup of the current configuration before performing the upgrade
  5. 5. Upload the new software image to the device or controller
  6. 6. Execute the upgrade command or use the vManage interface to install the new software image
  7. 7. After upgrade, verify the device is running version 18.3.0 or later using the 'show version' command in the CLI
  8. 8. Verify the 'request admin-tech' command now properly validates input and does not allow arbitrary file overwriting
Caveat Upgrading between major releases may require careful planning; ensure compatibility with other SD-WAN components and review Cisco's release notes for any configuration changes or migration requirements

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

Fix this in Vbond Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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