# CVE-2018-0372: Denial of service in Cisco Nexus 9000 Series unknown

> Remote attackers can cause a denial of service on Cisco Nexus switches by sending malicious DHCPv6 packets when unicast routing is enabled.

- **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-76q4-cmwx-wvmq

## What is CVE-2018-0372?

CVE-2018-0372 is a high-severity denial of service vulnerability in Cisco Nx-Os, 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 DHCPv6 feature of the Cisco Nexus 9000 Series Fabric Switches in Application-Centric Infrastructure (ACI) Mode could allow an unauthenticated, remote attacker to cause the device to run low on system memory, which could result in a Denial of Service (DoS) condition on an affected system. The vulnerability is due to improper memory management when DHCPv6 packets are received on an interface of the targeted device. An attacker could exploit this vulnerability by sending a high number of malicious DHCPv6 packets to be processed by an affected device. A successful exploit could allow the attacker to cause the system to run low on memory, which could cause an eventual reboot of an affected device. The vulnerability only applies to IPv6 protocol packets and not for IPv4 protocol packets. This vulnerability affects Cisco Nexus 9000 Series Fabric Switches in ACI Mode running software version 13.0(1k). The vulnerability can only be exploited when unicast routing is enabled on the Bridge Domain (BD). DHCP and DHCP relay do not have to be configured for the vulnerability to be exploited. Cisco Bug IDs: CSCvg38918.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Cisco Nx-Os.

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

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

## Is CVE-2018-0372 being exploited?

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

## Other vulnerabilities in Cisco Nx-Os

- [CVE-2024-20399](https://insights.sbomify.com/CVE-2024-20399/): Cisco NX-OS Command Injection (medium 6.0, exploited in the wild)
- [CVE-2021-1361](https://insights.sbomify.com/CVE-2021-1361/): Cisco NX-OS Software Unauthenticated Arbitrary File Actions Vulnerability (critical 9.8)
- [CVE-2018-0301](https://insights.sbomify.com/CVE-2018-0301/): Memory corruption in Cisco NX-OS unknown (critical 9.8)
- [CVE-2016-1453](https://insights.sbomify.com/CVE-2016-1453/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-1341](https://insights.sbomify.com/CVE-2016-1341/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0372 is a high-severity denial of service vulnerability in Cisco Nx-Os, 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-0372 in the wild and no public exploit code.

Affected product: Cisco Nx-Os. 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-0372/ (Markdown: https://insights.sbomify.com/CVE-2018-0372/index.md)
```

## Sources

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

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