# CVE-2019-12662: Cisco NX-OS and IOS XE Software Virtual Service Image Signature Bypass Vulnerability

> Authenticated local attackers can bypass signature verification to load malicious OVA images, enabling code execution on Cisco network devices.

- **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:** 25 Sep 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-pqr2-367x-jwhw

## What is CVE-2019-12662?

CVE-2019-12662 is a medium-severity vulnerability in Cisco Ios Xe, published on 25 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Cisco NX-OS Software and Cisco IOS XE Software could allow an authenticated, local attacker with valid administrator or privilege level 15 credentials to load a virtual service image and bypass signature verification on an affected device. The vulnerability is due to improper signature verification during the installation of an Open Virtual Appliance (OVA) image. An authenticated, local attacker could exploit this vulnerability and load a malicious, unsigned OVA image on an affected device. A successful exploit could allow an attacker to perform code execution on a crafted software OVA image.

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

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

It affects 52 products.


Products: Cisco Ios Xe, Cisco Nexus 3016 Firmware, Cisco Nexus 3048 Firmware, Cisco Nexus 3064-T Firmware, Cisco Nexus 3064 Firmware, Cisco Nexus 31108pc-v Firmware, Cisco Nexus 31108tc-v Firmware, Cisco Nexus 31128pq Firmware, Cisco Nexus 3132c-Z Firmware, Cisco Nexus 3132q-v Firmware, Cisco Nexus 3132q-Xl Firmware, Cisco Nexus 3132q Firmware, Cisco Nexus 3164q Firmware, Cisco Nexus 3172 Firmware, Cisco Nexus 3172pq-Xl Firmware, Cisco Nexus 3172tq-32t Firmware, Cisco Nexus 3172tq-Xl Firmware, Cisco Nexus 3172tq Firmware, Cisco Nexus 3232c Firmware, Cisco Nexus 3264c-E Firmware and 32 more.

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

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

## Is CVE-2019-12662 being exploited?

There is no known exploitation of CVE-2019-12662 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Ios Xe

- [CVE-2023-20198](https://insights.sbomify.com/CVE-2023-20198/): Cisco IOS XE Web UI Privilege Escalation (critical 10.0, exploited in the wild)
- [CVE-2018-0151](https://insights.sbomify.com/CVE-2018-0151/): Cisco IOS Software and Cisco IOS XE Software Quality of Service Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-20273](https://insights.sbomify.com/CVE-2023-20273/): Cisco IOS XE Web UI Command Injection (high 7.2, exploited in the wild)
- [CVE-2025-20188](https://insights.sbomify.com/CVE-2025-20188/): Hardcoded credentials in Cisco IOS XE Software (critical 10.0)
- [CVE-2021-34770](https://insights.sbomify.com/CVE-2021-34770/): Cisco IOS XE Software for Catalyst 9000 Family Wireless Controllers CAPWAP Remote Code Execution Vulnerability (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12662 and fix it if it is affected.

What it is: CVE-2019-12662 is a medium-severity vulnerability in Cisco Ios Xe, published on 25 Sep 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-12662 in the wild and no public exploit code.

Affected product: Cisco Ios Xe. 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-12662/ (Markdown: https://insights.sbomify.com/CVE-2019-12662/index.md)
```

## Sources

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

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