CVE intelligence and bounded remediation

CVE-2024-20280 — Cisco Ucs Central Software security vulnerability

Medium CVSS 6.3

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
Medium
CVSS
6.3 (3.1)
Published
2024-10-16
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-321, CWE-798

Affected products

  • cisco / ucs_central_software / 1.0(1a)
  • cisco / ucs_central_software / 1.1(1a)
  • cisco / ucs_central_software / 1.1(1b)
  • cisco / ucs_central_software / 1.1(2a)
  • cisco / ucs_central_software / 1.2(1a)
  • cisco / ucs_central_software / 1.2(1d)

Showing 6 representative product identities from 38 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Authentication bypass and missing authentication

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map every affected endpoint and protocol path, including alternate ports, legacy routes, recovery flows, service accounts, and machine-to-machine access.
  • Confirm which deployments enable the affected authentication mode and whether the interface is reachable from untrusted networks.
  • Review session, token, credential, and proxy trust configuration without attempting account takeover.

Remediate safely

  • Apply the supported fix and centralize fail-closed authentication before protected request handling.
  • Remove default or embedded credentials, rotate affected secrets and sessions, and bind authentication decisions to the intended audience and channel.
  • Add negative tests for alternate routes, malformed or absent credentials, recovery flows, and proxy-derived identity.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.