# CVE-2018-0292: Memory corruption in Cisco NX-OS unknown

> Unauthenticated adjacent attackers can execute arbitrary code or cause denial of service via crafted IGMP packets on Cisco Nexus switches with IGMP Snooping enabled.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-654c-89hm-cqcw

## What is CVE-2018-0292?

CVE-2018-0292 is a high-severity memory corruption vulnerability in Cisco Nx-Os, published on 20 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the Internet Group Management Protocol (IGMP) Snooping feature of Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to execute arbitrary code and gain full control of an affected system. The attacker could also cause an affected system to reload, resulting in a denial of service (DoS) condition. The vulnerability is due to a buffer overflow condition in the IGMP Snooping subsystem. An attacker could exploit this vulnerability by sending crafted IGMP packets to an affected system. An exploit could allow the attacker to execute arbitrary code and gain full control of the affected system or cause the affected system to reload, resulting in a DoS condition. This vulnerability affects Nexus 2000 Series Switches, Nexus 3000 Series Switches, Nexus 3500 Platform Switches, Nexus 3600 Platform Switches, Nexus 5500 Platform Switches, Nexus 5600 Platform Switches, Nexus 6000 Series Switches, Nexus 7000 Series Switches, Nexus 7700 Series Switches, Nexus 9000 Series Fabric Switches in Application Centric Infrastructure (ACI) mode, Nexus 9000 Series Switches in standalone NX-OS mode. Cisco Bug IDs: CSCuv79620, CSCvg71263.

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

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

It affects 1 product.


Products: Cisco Nx-Os.

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

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

## Is CVE-2018-0292 being exploited?

There is no known exploitation of CVE-2018-0292 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-0292 and fix it if it is affected.

What it is: CVE-2018-0292 is a high-severity memory corruption vulnerability in Cisco Nx-Os, published on 20 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0292 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-0292/ (Markdown: https://insights.sbomify.com/CVE-2018-0292/index.md)
```

## Sources

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

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