Cisco FXOS Software and UCS Manager Software Configuration Backup Static Key Vulnerability
A vulnerability in the backup configuration feature of Cisco UCS Manager Software and in the configuration export feature of Cisco FXOS Software could allow an unauthenticated attacker with access to a backup file to decrypt sensitive information stored in the full state and configuration backup files. This vulnerability is due to a weakness in the encryption method used for the backup function. An attacker could exploit this vulnerability by leveraging a static key used for the backup configuration feature. A successful exploit could allow the attacker to decrypt sensitive information that is stored in full state and configuration backup files, such as local user credentials, authentication server passwords, Simple Network Management Protocol (SNMP) community names, and other credentials.
- Published
- Feb 23, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-321
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · cisco
- 6.3
- 0.2 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| cisco | ucs central software | cpe:2.3:a:cisco:ucs_central_software |
| cisco | ucs 6536 firmware | cpe:2.3:o:cisco:ucs_6536_firmware |
| cisco | ucs 6536 | cpe:2.3:h:cisco:ucs_6536 |
| cisco | ucs 64108 firmware | cpe:2.3:o:cisco:ucs_64108_firmware |
| cisco | ucs 64108 | cpe:2.3:h:cisco:ucs_64108 |
| cisco | ucs 6454 firmware | cpe:2.3:o:cisco:ucs_6454_firmware |
| cisco | ucs 6454 | cpe:2.3:h:cisco:ucs_6454 |
| cisco | ucs 6200 firmware | cpe:2.3:o:cisco:ucs_6200_firmware |
| cisco | ucs 6200 | cpe:2.3:h:cisco:ucs_6200 |
| cisco | ucs 6248up firmware | cpe:2.3:o:cisco:ucs_6248up_firmware |
| cisco | ucs 6248up | cpe:2.3:h:cisco:ucs_6248up |
| cisco | ucs 6296up firmware | cpe:2.3:o:cisco:ucs_6296up_firmware |
and 27 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cisco fxosbefore 2.6.1
- cisco ucs 6200 firmwareall versions
- cisco ucs 6248up firmwareall versions
- cisco ucs 6296up firmwareall versions
- cisco ucs 6300 firmwareall versions
- cisco ucs 6324 firmwareall versions
- cisco ucs 6332 firmwareall versions
- cisco ucs 6332-16up firmwareall versions
- cisco ucs 64108 firmwareall versions
- cisco ucs 6454 firmwareall versions
- cisco ucs 6536 firmwareall versions
- cisco ucs central softwarebefore 4.2\(3c\)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (cisco). Independent of NVD's CPE analysis and usually ahead of it.
Cisco Cisco Unified Computing System (Managed)
- n/aaffected
Same product
cisco: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-20015Cisco Firepower 4100 Series, Firepower 9300 Security Appliances, and UCS Fabric Interconnects Command Injection Vulnerability26Monitor
- CVE-2024-20280Cisco UCS Central Software Configuration Backup Static Key Vulnerability25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-321 · Use of Hard-coded Cryptographic KeyCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.