# CVE-2019-1620: Cisco Data Center Network Manager Arbitrary File Upload and Remote Code Execution Vulnerability

> Unauthenticated attackers can upload arbitrary files to Cisco DCNM, leading to remote code execution with root privileges.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2019
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-5r5x-3gwj-56vr

## What is CVE-2019-1620?

CVE-2019-1620 is a critical vulnerability in Cisco Data Center Network Manager, published on 27 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to upload arbitrary files on an affected device. The vulnerability is due to incorrect permission settings in affected DCNM software. An attacker could exploit this vulnerability by uploading specially crafted data to the affected device. A successful exploit could allow the attacker to write arbitrary files on the filesystem and execute code with root privileges on the affected device.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-264

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

It affects 1 product.


Products: Cisco Data Center Network Manager.

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

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

## Is CVE-2019-1620 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1620 exists.

Public exploit code:

- Cisco Data Center Network Manager Unauthenticated Remote Code Execution (metasploit)
- Cisco Data Center Network Manager - Unauthenticated Remote Code Execution (Metasploit) (exploitdb)
- Cisco Data Center Network Manager - Unauthenticated Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Cisco Data Center Network Manager

- [CVE-2020-3382](https://insights.sbomify.com/CVE-2020-3382/): Cisco Data Center Network Manager Authentication Bypass Vulnerability (critical 9.8)
- [CVE-2019-15975](https://insights.sbomify.com/CVE-2019-15975/): Cisco Data Center Network Manager Authentication Bypass Vulnerabilities (critical 9.8)
- [CVE-2019-15976](https://insights.sbomify.com/CVE-2019-15976/): Cisco Data Center Network Manager Authentication Bypass Vulnerabilities (critical 9.8)
- [CVE-2019-15977](https://insights.sbomify.com/CVE-2019-15977/): Cisco Data Center Network Manager Authentication Bypass Vulnerabilities (critical 9.8)
- [CVE-2019-1619](https://insights.sbomify.com/CVE-2019-1619/): Cisco Data Center Network Manager Authentication Bypass Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1620 is a critical vulnerability in Cisco Data Center Network Manager, published on 27 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1620 exists.

Affected product: Cisco Data Center Network Manager. 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-1620/ (Markdown: https://insights.sbomify.com/CVE-2019-1620/index.md)
```

## Sources

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

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