Vbond OrchestratorApplication · Cisco
CVE-2018-0343
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 · uneditedA vulnerability in the configuration and management service of the Cisco SD-WAN Solution could allow an authenticated, remote attacker to execute arbitrary code with vmanage user privileges or cause a denial of service (DoS) condition on an affected system. The vulnerability is due to insufficient access restrictions to the HTTP management interface of the affected solution. An attacker could exploit this vulnerability by sending a malicious HTTP request to the affected management service through an authenticated device. A successful exploit could allow the attacker to execute arbitrary code with vmanage user privileges or stop HTTP services 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: CSCvi69976.
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 confidenceA vulnerability in the Cisco SD-WAN Solution's configuration and management service (affecting vManage, vBond, vEdge series, and vSmart) allows an authenticated, remote attacker to execute arbitrary code with vmanage user privileges or cause DoS via malicious HTTP requests to the management interface. The root cause is insufficient access restrictions on the HTTP management interface.
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
all versions
Vedge PlusWeb browser
all versions
Vedge ProWeb browser
all versions
Vmanage Network ManagementApplication
all versions
Vsmart ControllerApplication
all versions
Vedge 100 FirmwareOperating system
< 18.3.0
Vedge 100b FirmwareOperating system
< 18.3.0
Vedge 100m FirmwareOperating system
< 18.3.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco SD-WAN components in the environmentLook for running processes or services named vmanage, vbond, vsmart, or vedge. Check network listeners on common management ports (443, 8443). Use commands like 'netstat -tulpn' or 'ps aux | grep -i v' on Linux systems.Affected if Any of the following processes/services are found: vmanage, vbond, vsmart, or vedge instances are running in the environment.
-
Confirm the specific SD-WAN product typeQuery the system or network inventory to identify which Cisco SD-WAN products are deployed: Vbond Orchestrator, Vedge Plus, Vedge Pro, Vmanage Network Management, Vsmart Controller, or Vedge 100 series firmware.Affected if The environment contains any of: Vbond Orchestrator, Vedge Plus, Vedge Pro, Vmanage Network Management, Vsmart Controller, or Vedge 100 series devices.
-
Check Vedge 100 firmware versionFor Vedge 100, 100b, or 100m devices, run 'show version' or access the device CLI to retrieve the firmware version. Compare against 18.3.0.Affected if The Vedge 100 series firmware version is below 18.3.0.
-
Verify HTTP management interface exposureCheck if the HTTP management interface is listening and accessible on the network. Look for HTTP (port 80) or HTTP alternate ports on the SD-WAN device management IPs. Use 'netstat -an | grep :80' or scan management interfaces.Affected if The HTTP management interface is exposed and accessible over the network without additional network segmentation.
-
Confirm authentication status on management interfaceReview access control lists, firewall rules, or device configuration to determine if the management interface permits unauthenticated or weakly authenticated access. Check if the vmanage user account exists and its privilege level.Affected if The management interface allows authenticated access with vmanage user privileges, which is the default vulnerable configuration.
A system is affected if it runs any Cisco SD-WAN product (Vbond, Vedge, Vmanage, or Vsmart) with the HTTP management interface exposed, or if Vedge 100 series firmware is below version 18.3.0.
Generated from the published advisory. Verify against your own configuration.
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 data18.3.0
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
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-0343 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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