dbcve.org
Vbond OrchestratorApplication · Cisco

CVE-2018-0344

HIGH · 7.2 CVSS v3.0 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 vManage dashboard for the configuration and management service of the Cisco SD-WAN Solution could allow an authenticated, remote attacker to inject and execute arbitrary commands with vmanage user privileges on an affected system. The vulnerability is due to insufficient input validation of data parameters for certain fields in the affected solution. An attacker could exploit this vulnerability by configuring a malicious username on the login page of the affected solution. A successful exploit could allow the attacker to inject and execute arbitrary commands with vmanage user privileges on an affected system. 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: CSCvi69974.

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 Cisco SD-WAN vManage dashboard's login page allows authenticated attackers to inject arbitrary OS commands via insufficiently validated username parameters, executing with vmanage user privileges.

MitigationUpgrade to Cisco SD-WAN Solution Release 18.3.0 or later to obtain the patch for insufficient input validation in the login page parameter handling.

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.0/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 installed SD-WAN component
    Log into the vManage web UI or use CLI to determine which Cisco SD-WAN component is running. Check the system information or version page for product name (Vbond Orchestrator, Vedge Plus, Vedge Pro, Vmanage Network Management, Vsmart Controller, or Vedge 100/100b/100m).
    Affected if The system is running any of the listed affected products with all versions, or Vedge 100/100b/100m with firmware version below 18.3.0
  2. Check Vedge firmware version
    For Vedge devices, access the device CLI and run the command 'show version' or access vManage to view device inventory and firmware version details.
    Affected if The Vedge firmware version is lower than 18.3.0 for models 100, 100b, or 100m
  3. Verify vManage login interface accessibility
    Confirm the vManage web interface is accessible by attempting to reach the login page via HTTPS on the management IP address (default port 8443 or 443).
    Affected if The vManage login page is exposed and reachable on the network
  4. Confirm authentication is enabled
    Check the vManage system settings or authentication configuration to verify that user authentication is enabled on the login page.
    Affected if User authentication is enabled on the vManage login page, which is the default configuration

A system is affected if it runs any Cisco SD-WAN component from the affected product list (all versions for most products, or Vedge firmware below 18.3.0) and has the vManage login interface accessible with authentication enabled.

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 obtain the patch for insufficient input validation in the login page parameter handling.

Fix this in Vbond Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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