# CVE-2018-0345: Command injection in Cisco SD-WAN Solution unknown

> Authenticated attackers can execute arbitrary commands as the vmanage user in Cisco SD-WAN due to insufficient input validation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-6x3g-4r88-c5qh

## What is CVE-2018-0345?

CVE-2018-0345 is a high-severity command injection vulnerability in Cisco SD-WAN Solution unknown, published on 18 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the configuration and management database of the Cisco SD-WAN Solution could allow an authenticated, remote attacker to execute arbitrary commands with the privileges of the vmanage user in the configuration management system of the affected software. The vulnerability is due to insufficient validation of command arguments that are passed to the configuration and management database of the affected software. An attacker could exploit this vulnerability by creating custom functions that contain malicious code and are executed as the vmanage user of the configuration management system. A successful exploit could allow the attacker to execute arbitrary commands with the privileges of the vmanage user in the configuration management system of the affected software. 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, vManage Network Management Software, vSmart Controller Software. Cisco Bug IDs: CSCvi69937.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-0345?

It affects 12 products.


Products: Cisco Vbond Orchestrator, Cisco Vedge-1000 Firmware, Cisco Vedge-100 Firmware, Cisco Vedge-2000 Firmware, Cisco Vedge-5000 Firmware, Cisco Vedge-Plus, Cisco Vedge-Pro, Cisco Vedge 100b Firmware, Cisco Vedge 100m Firmware, Cisco Vedge 100wm Firmware, Cisco Vmanage Network Management, Cisco Vsmart Controller.

## How do I fix CVE-2018-0345?

No fix has been published for CVE-2018-0345 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-0345 being exploited?

There is no known exploitation of CVE-2018-0345 in the wild and no public exploit code.

## Other vulnerabilities in Cisco SD-WAN Solution unknown

- [CVE-2018-0349](https://insights.sbomify.com/CVE-2018-0349/): Command injection in Cisco SD-WAN Solution unknown (critical 9.8)
- [CVE-2018-0343](https://insights.sbomify.com/CVE-2018-0343/): Missing authorization in Cisco SD-WAN Solution unknown (high 8.8)
- [CVE-2018-0350](https://insights.sbomify.com/CVE-2018-0350/): Command injection in Cisco SD-WAN Solution unknown (high 8.8)
- [CVE-2018-0433](https://insights.sbomify.com/CVE-2018-0433/): Cisco SD-WAN Solution Command Injection Vulnerability (high 7.8)
- [CVE-2018-0347](https://insights.sbomify.com/CVE-2018-0347/): Command injection in Cisco SD-WAN Solution unknown (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0345 and fix it if it is affected.

What it is: CVE-2018-0345 is a high-severity command injection vulnerability in Cisco SD-WAN Solution unknown, published on 18 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0345 in the wild and no public exploit code.

Affected product: Cisco SD-WAN Solution unknown. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-0345/ (Markdown: https://insights.sbomify.com/CVE-2018-0345/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0345
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0345
- OSV: https://osv.dev/vulnerability/CVE-2018-0345

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-0345/
Summaries are generated and may contain mistakes; the official description above is the record.