# CVE-2020-3504: Cisco UCS Manager Software Local Management CLI Denial of Service Vulnerability

> An authenticated local attacker can cause a denial of service in Cisco UCS Manager by executing specific CLI commands that lead to process buildup.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 27 Aug 2020
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-pvcf-6vj4-mpr5

## What is CVE-2020-3504?

CVE-2020-3504 is a low-severity denial of service vulnerability in Cisco Firepower Extensible Operating System, published on 27 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the local management (local-mgmt) CLI of Cisco UCS Manager Software could allow an authenticated, local attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to improper handling of CLI command parameters. An attacker could exploit this vulnerability by executing specific commands on the local-mgmt CLI on an affected device. A successful exploit could allow the attacker to cause internal system processes to fail to terminate properly, which could result in a buildup of stuck processes and lead to slowness in accessing the UCS Manager CLI and web UI. A sustained attack may result in a restart of internal UCS Manager processes and a temporary loss of access to the UCS Manager CLI and web UI.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-664 (Improper Control of a Resource Through its Lifetime)

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

It affects 2 products.


Products: Cisco Firepower Extensible Operating System, Cisco Nx-Os.

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

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

## Is CVE-2020-3504 being exploited?

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

## Other vulnerabilities in Cisco Firepower Extensible Operating System

- [CVE-2018-0310](https://insights.sbomify.com/CVE-2018-0310/): Information disclosure in Cisco FXOS and NX-OS unknown (critical 9.8)
- [CVE-2015-6435](https://insights.sbomify.com/CVE-2015-6435/): Command injection in n/a (critical 9.8)
- [CVE-2021-1368](https://insights.sbomify.com/CVE-2021-1368/): Memory corruption in Cisco NX-OS Software (high 8.8)
- [CVE-2020-3456](https://insights.sbomify.com/CVE-2020-3456/): Cisco FXOS Software Firepower Chassis Manager Cross-Site Request Forgery Vulnerability (high 8.8)
- [CVE-2020-3172](https://insights.sbomify.com/CVE-2020-3172/): Cisco FXOS and NX-OS Software Cisco Discovery Protocol Arbitrary Code Execution and Denial of Service Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-3504 is a low-severity denial of service vulnerability in Cisco Firepower Extensible Operating System, published on 27 Aug 2020. 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-2020-3504 in the wild and no public exploit code.

Affected product: Cisco Firepower Extensible Operating System. 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-3504/ (Markdown: https://insights.sbomify.com/CVE-2020-3504/index.md)
```

## Sources

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

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