CVE-2024-20365

6.5 MEDIUM

📋 TL;DR

This vulnerability allows authenticated administrators to execute arbitrary commands through the Redfish API on affected Cisco UCS servers, potentially gaining root access. It affects Cisco UCS B-Series, C-Series Managed, and X-Series servers with insufficient input validation in their Redfish implementation.

💻 Affected Systems

Products:
  • Cisco UCS B-Series Servers
  • Cisco UCS Managed C-Series Servers
  • Cisco UCS X-Series Servers
Versions: Specific versions not provided in advisory; check Cisco advisory for exact affected versions
Operating Systems: Cisco UCS firmware/management software
Default Config Vulnerable: ⚠️ Yes
Notes: Requires Redfish API access and administrative credentials; affects management interfaces rather than guest operating systems

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker with administrative credentials gains full root control over the server, allowing complete system compromise, data theft, and persistent backdoor installation.

🟠

Likely Case

Malicious insiders or compromised admin accounts exploit the vulnerability to escalate privileges and maintain persistence within the infrastructure.

🟢

If Mitigated

With proper access controls and network segmentation, exploitation is limited to authorized administrators, reducing overall risk.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires administrative credentials but involves simple command injection through crafted API requests

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Cisco advisory for specific fixed versions

Vendor Advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cimc-redfish-cominj-sbkv5ZZ

Restart Required: Yes

Instructions:

1. Review Cisco advisory for affected versions. 2. Download and apply appropriate firmware updates from Cisco. 3. Reboot affected servers after patching. 4. Verify patch application through version checks.

🔧 Temporary Workarounds

Restrict Redfish API Access

all

Limit network access to Redfish API endpoints to trusted management networks only

Configure firewall rules to restrict access to Redfish ports (typically 443/HTTPS)

Implement Strong Authentication Controls

all

Enforce multi-factor authentication and strict credential management for administrative accounts

Enable MFA for all administrative accounts accessing Redfish API

🧯 If You Can't Patch

  • Isolate affected servers in dedicated management VLANs with strict network segmentation
  • Implement comprehensive monitoring and alerting for Redfish API access and command execution

🔍 How to Verify

Check if Vulnerable:

Check Cisco UCS firmware version against affected versions listed in Cisco advisory

Check Version:

Check through Cisco UCS Manager GUI or CLI; specific command varies by platform

Verify Fix Applied:

Verify firmware version has been updated to patched version listed in Cisco advisory

📡 Detection & Monitoring

Log Indicators:

  • Unusual Redfish API requests with command-like parameters
  • Multiple failed authentication attempts followed by successful admin login
  • Unexpected process execution from Redfish service context

Network Indicators:

  • Unusual traffic patterns to Redfish API endpoints
  • Command injection patterns in HTTP requests to Redfish endpoints

SIEM Query:

source="redfish" AND (command* OR exec* OR system* OR shell* IN request_body)

🔗 References

📤 Share & Export