cve.bz

CVE-2024-20280 cisco ucs central software: Use of Hard-coded Cryptographic Key

6.3 mediumEPSS 0.1%

Medium (6.3) in cisco ucs central software. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.3 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-321 Use of Hard-coded Cryptographic Key
CWE-798 Use of Hard-coded Credentials
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-20280 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-20280?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-20280?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-20280 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cisco:ucs_central_software1.0(1a)
cisco:ucs_central_software1.1(1a)
cisco:ucs_central_software1.1(1b)
cisco:ucs_central_software1.1(2a)
cisco:ucs_central_software1.2(1a)
cisco:ucs_central_software1.2(1d)
cisco:ucs_central_software1.2(1e)
cisco:ucs_central_software1.2(1f)
cisco:ucs_central_software1.3(1a)
cisco:ucs_central_software1.3(1b)
cisco:ucs_central_software1.3(1c)
cisco:ucs_central_software1.4(1a)
cisco:ucs_central_software1.4(1b)
cisco:ucs_central_software1.4(1c)
cisco:ucs_central_software1.5(1a)
cisco:ucs_central_software1.5(1b)
cisco:ucs_central_software1.5(1c)
cisco:ucs_central_software2.0(1a)
cisco:ucs_central_software2.0(1b)
cisco:ucs_central_software2.0(1c)
cisco:ucs_central_software2.0(1d)
cisco:ucs_central_software2.0(1e)
cisco:ucs_central_software2.0(1f)
cisco:ucs_central_software2.0(1g)
cisco:ucs_central_software2.0(1h)
cisco:ucs_central_software2.0(1i)
cisco:ucs_central_software2.0(1j)
cisco:ucs_central_software2.0(1k)
cisco:ucs_central_software2.0(1l)
cisco:ucs_central_software2.0(1m)
cisco:ucs_central_software2.0(1n)
cisco:ucs_central_software2.0(1o)
cisco:ucs_central_software2.0(1p)
cisco:ucs_central_software2.0(1q)
cisco:ucs_central_software2.0(1r)
cisco:ucs_central_software2.0(1s)
cisco:ucs_central_software2.0(1t)
cisco:ucs_central_software2.0(1u)

Attack patterns (CAPEC)

  • CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
  • CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON