Cisco UCS Central Software Configuration Backup Static Key Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A vulnerability in the backup feature of Cisco UCS Central Software could allow an attacker with access to a backup file to learn sensitive information that is stored in the full state and configuration backup files. This vulnerability is due to a weakness in the encryption method that is used for the backup function. An attacker could exploit this vulnerability by accessing a backup file and leveraging a static key that is used for the backup configuration feature. A successful exploit could allow an attacker with access to a backup file to learn sensitive information that is stored in full state backup files and configuration backup files, such as local user credentials, authentication server passwords, Simple Network Management Protocol (SNMP) community names, and the device SSL server certificate and key.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Cisco Cisco Unified Computing System Central Software
2.0(1e), 1.1(1b), 1.4(1b), 2.0(1a), 2.0(1h), 1.3(1a), 2.0(1g), 2.0(1c), 2.0(1k), 1.0(1a), 2.0(1l), 1.2(1f), 2.0(1f), 1.4(1c), 1.3(1c), 1.1(1a), 1.4(1a), 1.2(1a), 1.2(1d), 2.0(1j), 1.5(1c), 1.5(1a), 1.1(2a), 1.3(1b), 2.0(1b), 2.0(1i), 1.2(1e), 1.5(1b), 2.0(1d), 2.0(1m), and 8 more