# CVE-2018-0346: Memory corruption in Cisco SD-WAN Solution unknown

> Unauthenticated remote attackers can cause a denial of service on Cisco SD-WAN devices by sending malicious packets that trigger a buffer overflow.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-mgv5-gwhp-72c8

## What is CVE-2018-0346?

CVE-2018-0346 is a high-severity memory corruption vulnerability in Cisco SD-WAN Solution unknown, published on 18 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Zero Touch Provisioning service of the Cisco SD-WAN Solution could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to incorrect bounds checks for certain values in packets that are sent to the Zero Touch Provisioning service of the affected software. An attacker could exploit this vulnerability by sending malicious packets to the affected software for processing. When the software processes the packets, a buffer overflow condition could occur and cause an affected device to reload. A successful exploit could allow the attacker to cause a temporary DoS condition while the device reloads. This vulnerability can be exploited only by traffic that is destined for an affected device. It cannot be exploited by traffic that is transiting a 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, vManage Network Management Software, vSmart Controller Software. Cisco Bug IDs: CSCvi69914.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

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-0346?

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

## Is CVE-2018-0346 being exploited?

There is no known exploitation of CVE-2018-0346 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-0345](https://insights.sbomify.com/CVE-2018-0345/): Command injection 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0346 is a high-severity memory corruption vulnerability in Cisco SD-WAN Solution unknown, published on 18 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0346 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-0346/ (Markdown: https://insights.sbomify.com/CVE-2018-0346/index.md)
```

## Sources

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

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