# CVE-2019-1795: Cisco FXOS and NX-OS Software Command Injection Vulnerability

> An authenticated local attacker can execute arbitrary commands with root privileges on Cisco NX-OS devices via insufficient CLI argument validation.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-wq4q-6hpg-5cr3

## What is CVE-2019-1795?

CVE-2019-1795 is a medium-severity command injection vulnerability in Cisco Firepower Extensible Operating System, published on 15 May 2019. 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 of Cisco FXOS Software and Cisco NX-OS Software could allow an authenticated, local attacker to execute arbitrary commands on the underlying Linux operating system with the privilege level of root. The vulnerability is due to insufficient validation of arguments passed to a specific CLI command on the affected device. An attacker could exploit this vulnerability by including malicious input as the argument of an affected command. A successful exploit could allow the attacker to execute arbitrary commands on the underlying Linux operating system with elevated privileges. An attacker would need valid administrator credentials to exploit this vulnerability.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2019-1795?

It affects 2 products.


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

## How do I fix CVE-2019-1795?

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

## Is CVE-2019-1795 being exploited?

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

What it is: CVE-2019-1795 is a medium-severity command injection vulnerability in Cisco Firepower Extensible Operating System, published on 15 May 2019. 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-2019-1795 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-2019-1795/ (Markdown: https://insights.sbomify.com/CVE-2019-1795/index.md)
```

## Sources

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

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