# CVE-2020-3470: Cisco Integrated Management Controller Multiple Remote Code Execution Vulnerabilities

> Unauthenticated remote attackers can execute arbitrary code with root privileges via crafted HTTP requests to the Cisco IMC API subsystem.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 18 Nov 2020
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-q622-qgp9-63h7

## What is CVE-2020-3470?

CVE-2020-3470 is a critical memory corruption vulnerability in Cisco Unified Computing System (Standalone), published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple vulnerabilities in the API subsystem of Cisco Integrated Management Controller (IMC) could allow an unauthenticated, remote attacker to execute arbitrary code with root privileges. The vulnerabilities are due to improper boundary checks for certain user-supplied input. An attacker could exploit these vulnerabilities by sending a crafted HTTP request to the API subsystem of an affected system. When this request is processed, an exploitable buffer overflow condition may occur. A successful exploit could allow the attacker to execute arbitrary code with root privileges on the underlying operating system (OS).

Weakness: CWE-20 (Improper Input Validation), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2020-3470?

It affects 2 products.


Products: Cisco Enterprise Nfv Infrastructure Software, Cisco Integrated Management Controller.

## How do I fix CVE-2020-3470?

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

## Is CVE-2020-3470 being exploited?

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

## Other vulnerabilities in Cisco Unified Computing System (Standalone)

- [CVE-2022-20777](https://insights.sbomify.com/CVE-2022-20777/): Cisco Enterprise NFV Infrastructure Software Vulnerabilities (critical 9.9)
- [CVE-2022-20779](https://insights.sbomify.com/CVE-2022-20779/): Cisco Enterprise NFV Infrastructure Software Vulnerabilities (critical 9.9)
- [CVE-2022-20780](https://insights.sbomify.com/CVE-2022-20780/): Cisco Enterprise NFV Infrastructure Software Vulnerabilities (critical 9.9)
- [CVE-2021-34746](https://insights.sbomify.com/CVE-2021-34746/): Cisco Enterprise NFV Infrastructure Software Authentication Bypass Vulnerability (critical 9.8)
- [CVE-2019-1895](https://insights.sbomify.com/CVE-2019-1895/): Cisco Enterprise NFV Infrastructure Software VNC Authentication Bypass Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3470 and fix it if it is affected.

What it is: CVE-2020-3470 is a critical memory corruption vulnerability in Cisco Unified Computing System (Standalone), published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3470 in the wild and no public exploit code.

Affected product: Cisco Unified Computing System (Standalone). 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-2020-3470/ (Markdown: https://insights.sbomify.com/CVE-2020-3470/index.md)
```

## Sources

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

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