dbcve.org
Vbond OrchestratorApplication · Cisco

CVE-2018-0342

MEDIUM · 6.7 CVSS v3.0 Published 2018-07-18
Fix available
A fix is available. Upgrade to 18.3.0 or later.
See remediation →
69/100
Remediation priority · Elevated
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 configuration and monitoring service of the Cisco SD-WAN Solution could allow an authenticated, local attacker to execute arbitrary code with root privileges or cause a denial of service (DoS) condition on an affected device. The vulnerability is due to incomplete bounds checks for data that is provided by the configuration and monitoring service of the affected solution. An attacker could exploit this vulnerability by sending malicious data to the vDaemon listening service on an affected device. A successful exploit could allow the attacker to cause a buffer overflow condition on the affected device, which could allow the attacker to execute arbitrary code with root privileges on the device or cause the vDaemon listening service to reload and result in a DoS condition on the device. 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: CSCvi70003.

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 buffer overflow vulnerability exists in the vDaemon configuration and monitoring service of Cisco SD-WAN Solution due to incomplete bounds checking on user-supplied data. An authenticated local attacker can send malicious data to the vDaemon listening service, causing overflow conditions that allow arbitrary code execution with root privileges or denial of service via service reload.

MitigationUpgrade to Cisco SD-WAN Release 18.3.0 or later, which contains the fix for this vulnerability. Prior to upgrade, restrict local authenticated access to trusted personnel only.

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

CVSS:3.0/AV:L/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 Cisco SD-WAN product type
    Determine which Cisco SD-WAN component is deployed: Vbond Orchestrator, Vedge Plus, Vedge Pro, Vmanage, Vsmart Controller, or Vedge 100 series hardware. Check system documentation or inventory for the product model.
    Affected if The product is any of: Vbond Orchestrator, Vedge Plus, Vedge Pro, Vmanage Network Management, Vsmart Controller, or Vedge 100/100b/100m hardware.
  2. Check the installed firmware or software version
    For Vedge 100 series hardware, run 'show version' or access the device management interface to view the firmware version. For software-based components (Vbond, Vmanage, Vsmart), check the installed software version via CLI or management interface.
    Affected if For Vedge 100/100b/100m: firmware version is earlier than 18.3.0. For Vbond, Vedge Plus, Vedge Pro, Vmanage, or Vsmart: all versions are affected.
  3. Verify vDaemon service status
    Check if the vDaemon service is running on the affected device. On Cisco SD-WAN devices, this may be visible in process listings or service status outputs. Use commands like 'show process' or check service logs if accessible.
    Affected if The vDaemon service is running and accessible for local authenticated connections.
  4. Confirm local authenticated access scope
    Review local user accounts and access controls on the SD-WAN device. Check which users have shell or administrative access to the device.
    Affected if More than trusted personnel have local authenticated access to the device, allowing potential attack execution.

If the system is any Cisco SD-WAN product (Vbond, Vedge Plus/Pro, Vmanage, Vsmart, or Vedge 100 series) and vDaemon is running with broader-than-intended local access, the environment may be affected; Vedge 100 series devices are affected if firmware is below 18.3.0.

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, which contains the fix for this vulnerability. Prior to upgrade, restrict local authenticated access to trusted personnel only.

Fix this in Vbond Orchestrator Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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