Cisco UCS Central Backup Static Key Encryption Leak
CVE-2024-20280 Published on October 16, 2024
Cisco UCS Central Software Configuration Backup Static Key Vulnerability
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.
Vulnerability Analysis
CVE-2024-20280 is exploitable with local system access, requires user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have a high impact on confidentiality, with no impact on integrity and availability.
Weakness Types
Use of Hard-coded Cryptographic Key
The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.
Use of Hard-coded Credentials
The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.
Products Associated with CVE-2024-20280
Want to know whenever a new CVE is published for Cisco Ucs Central Software? stack.watch will email you.
Affected Versions
Cisco Unified Computing System Central Software:- Version 2.0(1e) is affected.
- Version 1.1(1b) is affected.
- Version 1.4(1b) is affected.
- Version 2.0(1a) is affected.
- Version 2.0(1h) is affected.
- Version 1.3(1a) is affected.
- Version 2.0(1g) is affected.
- Version 2.0(1c) is affected.
- Version 2.0(1k) is affected.
- Version 1.0(1a) is affected.
- Version 2.0(1l) is affected.
- Version 1.2(1f) is affected.
- Version 2.0(1f) is affected.
- Version 1.4(1c) is affected.
- Version 1.3(1c) is affected.
- Version 1.1(1a) is affected.
- Version 1.4(1a) is affected.
- Version 1.2(1a) is affected.
- Version 1.2(1d) is affected.
- Version 2.0(1j) is affected.
- Version 1.5(1c) is affected.
- Version 1.5(1a) is affected.
- Version 1.1(2a) is affected.
- Version 1.3(1b) is affected.
- Version 2.0(1b) is affected.
- Version 2.0(1i) is affected.
- Version 1.2(1e) is affected.
- Version 1.5(1b) is affected.
- Version 2.0(1d) is affected.
- Version 2.0(1m) is affected.
- Version 2.0(1n) is affected.
- Version 2.0(1o) is affected.
- Version 2.0(1p) is affected.
- Version 2.0(1q) is affected.
- Version 2.0(1r) is affected.
- Version 2.0(1s) is affected.
- Version 2.0(1t) is affected.
- Version 2.0(1u) is affected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.