# CVE-2018-0330: Command injection in Cisco NX-OS unknown

> Authenticated attackers can execute commands with elevated privileges on Cisco NX-OS devices via the NX-API due to improper parameter validation.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 20 Jun 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-q8vc-mhxv-cp84

## What is CVE-2018-0330?

CVE-2018-0330 is a high-severity command injection vulnerability in Cisco Nx-Os, published on 20 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the NX-API management application programming interface (API) in devices running, or based on, Cisco NX-OS Software could allow an authenticated, remote attacker to execute commands with elevated privileges. The vulnerability is due to a failure to properly validate certain parameters included within an NX-API request. An attacker that can successfully authenticate to the NX-API could submit a request designed to bypass NX-OS role assignment. A successful exploit could allow the attacker to execute commands with elevated privileges. This vulnerability affects the following if configured to use the NX-API feature: MDS 9000 Series Multilayer Switches, Nexus 2000 Series Switches, Nexus 3000 Series Switches, Nexus 3500 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 Switches in standalone NX-OS mode. Cisco Bug IDs: CSCvc73177, CSCve40903, CSCve40911.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-264

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

It affects 1 product.


Products: Cisco Nx-Os.

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

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

## Is CVE-2018-0330 being exploited?

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

What it is: CVE-2018-0330 is a high-severity command injection vulnerability in Cisco Nx-Os, published on 20 Jun 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-0330 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-0330/ (Markdown: https://insights.sbomify.com/CVE-2018-0330/index.md)
```

## Sources

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

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