# CVE-2019-1615: Cisco NX-OS Software Image Signature Verification Vulnerability

> Authenticated local attackers can bypass image signature verification to install and boot malicious software on Cisco Nexus switches.

- **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:** 11 Mar 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-hq3r-r6cv-4q73

## What is CVE-2019-1615?

CVE-2019-1615 is a medium-severity vulnerability in Cisco Nx-Os, published on 11 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 Image Signature Verification feature of Cisco NX-OS Software could allow an authenticated, local attacker with administrator-level credentials to install a malicious software image on an affected device. The vulnerability is due to improper verification of digital signatures for software images. An attacker could exploit this vulnerability by loading an unsigned software image on an affected device. A successful exploit could allow the attacker to boot a malicious software image. Note: The fix for this vulnerability requires a BIOS upgrade as part of the software upgrade. For additional information, see the Details section of this advisory. Nexus 3000 Series Switches are affected running software versions prior to 7.0(3)I7(5). Nexus 9000 Series Fabric Switches in ACI Mode are affected running software versions prior to 13.2(1l). Nexus 9000 Series Switches in Standalone NX-OS Mode are affected running software versions prior to 7.0(3)I7(5). Nexus 9500 R-Series Line Cards and Fabric Modules are affected running software versions prior to 7.0(3)F3(5).

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Cisco Nx-Os.

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

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

## Is CVE-2019-1615 being exploited?

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

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

## Sources

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

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