# CVE-2023-20016: Cisco FXOS Software and UCS Manager Software Configuration Backup Static Key Vulnerability

> An attacker with access to backup files can decrypt sensitive credentials due to a static encryption key in Cisco UCS Manager and FXOS.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Feb 2023
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-xj38-cqqv-5f7w

## What is CVE-2023-20016?

CVE-2023-20016 is a medium-severity vulnerability in Cisco Unified Computing System (Managed), published on 23 Feb 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the backup configuration feature of Cisco UCS Manager Software and in the configuration export feature of Cisco FXOS Software could allow an unauthenticated attacker with access to a backup file to decrypt sensitive information stored in the full state and configuration backup files. This vulnerability is due to a weakness in the encryption method used for the backup function. An attacker could exploit this vulnerability by leveraging a static key used for the backup configuration feature. A successful exploit could allow the attacker to decrypt sensitive information that is stored in full state and configuration backup files, such as local user credentials, authentication server passwords, Simple Network Management Protocol (SNMP) community names, and other credentials.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 12 products.


Products: Cisco Fxos, 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-20016?

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

## Is CVE-2023-20016 being exploited?

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

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

- [CVE-2020-3171](https://insights.sbomify.com/CVE-2020-3171/): Cisco FXOS and UCS Manager Software Local Management CLI Command Injection Vulnerability (high 7.8)
- [CVE-2018-0300](https://insights.sbomify.com/CVE-2018-0300/): Path traversal in Cisco Firepower 4100 Series Next-Generation Firewall and Firepower 9300 Security Appliance unknown (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-20016 and fix it if it is affected.

What it is: CVE-2023-20016 is a medium-severity vulnerability in Cisco Unified Computing System (Managed), published on 23 Feb 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-20016 in the wild and no public exploit code.

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

## Sources

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

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