Credential disclosure via static backup encryption key
Published Feb 23, 2023 · Updated Oct 25, 2024
Static-key cryptographic failure in Cisco UCS Manager before 4.2(3d) allows attackers with a backup file to decrypt stored credentials. The backup function encrypts full-state and configuration backups with a static key, allowing that key to recover local-user, authentication-server, and SNMP secrets. Exploitation requires prior access to an exported backup file; it does not provide network access to the appliance or permit configuration changes.
Summary
What happened
Static-key cryptographic failure in Cisco UCS Manager before 4.2(3d) allows attackers with a backup file to decrypt stored credentials. The backup function encrypts full-state and configuration backups with a static key, allowing that key to recover local-user, authentication-server, and SNMP secrets. Exploitation requires prior access to an exported backup file; it does not provide network access to the appliance or permit configuration changes.
The record
- CVE
- CVE-2023-20016
- Published
- Feb 23, 2023
- Updated
- Oct 25, 2024
- Vendor
- ClamAV
- Product
- Cisco Unified Computing System (Managed)
- Classifications
- CWE-321, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2023CVE publishedPublication date reported by the CVE source.
- Oct 25, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo