# CVE-2023-20015: Command injection in Cisco Unified Computing System (Managed)

> Authenticated local attackers can inject commands into the CLI, potentially executing arbitrary code with root privileges on affected Cisco UCS Fabric Interconnects.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 23 Feb 2023
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-h6vq-xr3x-hmh3

## What is CVE-2023-20015?

CVE-2023-20015 is a medium-severity command injection vulnerability in Cisco Firepower Extensible Operating System, published on 23 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the CLI of Cisco Firepower 4100 Series, Cisco Firepower 9300 Security Appliances, and Cisco UCS 6200, 6300, 6400, and 6500 Series Fabric Interconnects could allow an authenticated, local attacker to inject unauthorized commands. This vulnerability is due to insufficient input validation of commands supplied by the user. An attacker could exploit this vulnerability by authenticating to a device and submitting crafted input to the affected command. A successful exploit could allow the attacker to execute unauthorized commands within the CLI. An attacker with Administrator privileges could also execute arbitrary commands on the underlying operating system of Cisco UCS 6400 and 6500 Series Fabric Interconnects with root-level privileges.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2023-20015?

It affects 12 products.


Products: Cisco Firepower Extensible Operating System, Cisco Ucs 6200 Firmware, Cisco Ucs 6248up Firmware, Cisco Ucs 6296up Firmware, Cisco Ucs 6300 Firmware, Cisco Ucs 6324 Firmware, Cisco Ucs 6332-16up Firmware, Cisco Ucs 6332 Firmware, Cisco Ucs 64108 Firmware, Cisco Ucs 6454 Firmware, Cisco Ucs 6536 Firmware, Cisco Ucs Central Software.

## How do I fix CVE-2023-20015?

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

## Is CVE-2023-20015 being exploited?

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

What it is: CVE-2023-20015 is a medium-severity command injection vulnerability in Cisco Firepower Extensible Operating System, published on 23 Feb 2023. 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-2023-20015 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-2023-20015/ (Markdown: https://insights.sbomify.com/CVE-2023-20015/index.md)
```

## Sources

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

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