# CVE-2018-0302: Memory corruption in Cisco FXOS Software and UCS Fabric Interconnect unknown

> Authenticated local attackers can trigger a buffer overflow in the CLI parser to execute arbitrary code with root privileges on Cisco FXOS and UCS devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-8989-fchh-h7r5

## What is CVE-2018-0302?

CVE-2018-0302 is a high-severity memory corruption vulnerability in Cisco Firepower Extensible Operating System, published on 21 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 CLI parser of Cisco FXOS Software and Cisco UCS Fabric Interconnect Software could allow an authenticated, local attacker to cause a buffer overflow on an affected device. The vulnerability is due to incorrect input validation in the CLI parser subsystem. An attacker could exploit this vulnerability by exceeding the expected length of user input. A successful exploit could allow the attacker to execute arbitrary code with root privileges on the affected system. This vulnerability affects Firepower 4100 Series Next-Generation Firewall, Firepower 9300 Security Appliance, UCS 6100 Series Fabric Interconnects, UCS 6200 Series Fabric Interconnects, UCS 6300 Series Fabric Interconnects. Cisco Bug IDs: CSCvb61099, CSCvb86743.

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

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

It affects 2 products.


Products: Cisco Firepower Extensible Operating System, Cisco Nx-Os.

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

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

## Is CVE-2018-0302 being exploited?

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

## Other vulnerabilities in Cisco Firepower Extensible Operating System

- [CVE-2018-0310](https://insights.sbomify.com/CVE-2018-0310/): Information disclosure in Cisco FXOS and NX-OS unknown (critical 9.8)
- [CVE-2015-6435](https://insights.sbomify.com/CVE-2015-6435/): Command injection in n/a (critical 9.8)
- [CVE-2021-1368](https://insights.sbomify.com/CVE-2021-1368/): Memory corruption in Cisco NX-OS Software (high 8.8)
- [CVE-2020-3456](https://insights.sbomify.com/CVE-2020-3456/): Cisco FXOS Software Firepower Chassis Manager Cross-Site Request Forgery Vulnerability (high 8.8)
- [CVE-2020-3172](https://insights.sbomify.com/CVE-2020-3172/): Cisco FXOS and NX-OS Software Cisco Discovery Protocol Arbitrary Code Execution and Denial of Service Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0302 is a high-severity memory corruption vulnerability in Cisco Firepower Extensible Operating System, published on 21 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-0302 in the wild and no public exploit code.

Affected product: Cisco Firepower Extensible Operating System. 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-0302/ (Markdown: https://insights.sbomify.com/CVE-2018-0302/index.md)
```

## Sources

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

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