dbcve.org
Vbond OrchestratorApplication · Cisco

CVE-2018-0347

HIGH · 7.8 CVSS v3.0 Published 2018-07-18
Fix available
A fix is available. Upgrade to 18.3.0 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 Zero Touch Provisioning (ZTP) subsystem of the Cisco SD-WAN Solution 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 malicious input to the affected parameter. The attacker must be authenticated to access the affected 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: vEdge 100 Series Routers, vEdge 1000 Series Routers, vEdge 2000 Series Routers, vEdge 5000 Series Routers. Cisco Bug IDs: CSCvi69906.

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 Zero Touch Provisioning (ZTP) subsystem of Cisco SD-WAN Solution allows an authenticated local attacker to inject arbitrary commands that execute with root privileges due to insufficient input validation on an affected parameter. The vulnerability affects vEdge 100, 1000, 2000, and 5000 Series Routers running releases prior to 18.3.0.

MitigationUpgrade to Cisco SD-WAN Solution Release 18.3.0 or later to remediate this vulnerability.

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

CVSS:3.0/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 vEdge device model
    Run 'show hardware' or check the device chassis to confirm it is a vEdge 100, 1000, 2000, or 5000 series router
    Affected if Device is NOT a vEdge 100/1000/2000/5000 series router (other models or product lines like Vbond, Vmanage, Vsmart are not affected by this specific vulnerability)
  2. Check the installed firmware version
    Run 'show version' or 'show system information' to display the running software version
    Affected if Firmware version is lower than 18.3.0 (versions 18.3.0 and later are patched)
  3. Confirm Zero Touch Provisioning is configured
    Run 'show configuration' or 'show running-config | include ztp' to check if ZTP is enabled
    Affected if ZTP subsystem is actively enabled on the device (the vulnerability only exists when ZTP is in use)
  4. Verify local authentication is available
    Check 'show configuration' or 'show aaa' to confirm local user accounts exist on the device
    Affected if Local authentication is enabled (the attacker needs valid local credentials to exploit this flaw)

A vEdge 100/1000/2000/5000 series router running firmware prior to 18.3.0 with ZTP enabled and local authentication configured is vulnerable to command injection via the ZTP subsystem.

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 Solution Release 18.3.0 or later to remediate this vulnerability.

Fix this in Vbond Orchestrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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