# CVE-2019-1601: Cisco NX-OS Software Unauthorized Filesystem Access Vulnerability

> An authenticated local attacker can modify restricted configuration files to bypass authentication and log in as any user on affected Cisco switches.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 8 Mar 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-w692-v48h-626c

## What is CVE-2019-1601?

CVE-2019-1601 is a high-severity missing authorization vulnerability in Cisco Nx-Os, published on 8 Mar 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 filesystem permissions of Cisco NX-OS Software could allow an authenticated, local attacker to gain read and write access to a critical configuration file. The vulnerability is due to a failure to impose strict filesystem permissions on the targeted device. An attacker could exploit this vulnerability by accessing and modifying restricted files. A successful exploit could allow an attacker to use the content of this configuration file to bypass authentication and log in as any user of the device. MDS 9000 Series Multilayer Switches are affected in versions prior to 6.2(25), 8.1(1b), and 8.3(1). Nexus 3000 Series Switches are affected in versions prior to 7.0(3)I4(9) and 7.0(3)I7(4). Nexus 3500 Platform Switches are affected in versions prior to 6.0(2)A8(10) and 7.0(3)I7(4). Nexus 3600 Platform Switches are affected in versions prior to 7.0(3)F3(5). Nexus 2000, 5500, 5600, and 6000 Series Switches are affected in versions prior to 7.1(5)N1(1b) and 7.3(3)N1(1). Nexus 7000 and 7700 Series Switches are affected in versions prior to 6.2(22), 7.3(3)D1(1), and 8.2(3). Nexus 9000 Series Switches-Standalone are affected in versions prior to 7.0(3)I4(9) and 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-732 (Incorrect Permission Assignment for Critical Resource), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Cisco Nx-Os.

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

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

## Is CVE-2019-1601 being exploited?

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

What it is: CVE-2019-1601 is a high-severity missing authorization vulnerability in Cisco Nx-Os, published on 8 Mar 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-1601 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-1601/ (Markdown: https://insights.sbomify.com/CVE-2019-1601/index.md)
```

## Sources

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

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