# CVE-2019-1604: Cisco NX-OS Software Privilege Escalation Vulnerability

> An authenticated local attacker can exploit an authorization logic error to execute commands with elevated privileges on Cisco Nexus switches.

- **Severity:** High 7.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Mar 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-jcrc-3h9p-854j

## What is CVE-2019-1604?

CVE-2019-1604 is a high-severity vulnerability in Cisco Nx-Os, published on 8 Mar 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the user account management interface of Cisco NX-OS Software could allow an authenticated, local attacker to gain elevated privileges on an affected device. The vulnerability is due to an incorrect authorization check of user accounts and their associated Group ID (GID). An attacker could exploit this vulnerability by taking advantage of a logic error that will permit the use of higher privileged commands than what is necessarily assigned. A successful exploit could allow an attacker to execute commands with elevated privileges on the underlying Linux shell of an affected device. Nexus 7000 and 7700 Series Switches are affected in versions prior to 6.2(22), 8.2(3), and 8.3(2). Nexus 3000 Series Switches are affected in versions prior to 7.0(3)I7(4). Nexus 3500 Platform Switches are affected in versions prior to 7.0(3)I7(4). Nexus 3600 Platform Switches are affected in versions prior to 7.0(3)F3(5). Nexus 9000 Series Switches-Standalone are affected in versions prior to 7.0(3)I7(4). Nexus 9500 R-Series Line Cards and Fabric Modules are affected in versions prior to 7.0(3)F3(5).

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Cisco Nx-Os.

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

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

## Is CVE-2019-1604 being exploited?

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

What it is: CVE-2019-1604 is a high-severity vulnerability in Cisco Nx-Os, published on 8 Mar 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1604 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-2019-1604/ (Markdown: https://insights.sbomify.com/CVE-2019-1604/index.md)
```

## Sources

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

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