AMI MegaRAC SPx Redfish Host Interface Authentication Bypass

Historical catalog analysis: CISA added this entry on June 25, 2025. The entry reflects catalog information retrieved on August 31, 2026, not a snapshot archived on the inclusion date. Check current vendor guidance before acting.

What the vulnerability is

CVE-2024-54085 is an authentication bypass vulnerability (CWE-290) identified in AMI MegaRAC SPx. The flaw exists within the Redfish Host Interface and allows for spoofing. If successfully exploited, this vulnerability could result in a loss of confidentiality, integrity, or availability of the affected system.

Exposure and applicability

This vulnerability affects systems utilizing the AMI MegaRAC SPx firmware. Because this is a proprietary implementation that may be integrated into various hardware products by different vendors, exposure is not limited to a single brand of server or motherboard. Organizations must identify assets where MegaRAC SPx is the underlying Baseboard Management Controller (BMC) firmware and specifically verify if the Redfish Host Interface is active and accessible.

Remediation priorities

Based on our analysis, vulnerability management teams should prioritize remediation based on the accessibility of the BMC network. The following actions are recommended:

1. Asset Identification: Identify all hardware utilizing AMI MegaRAC SPx. Because this component is often embedded by OEMs, defenders should consult hardware manifests and vendor-specific security advisories to determine applicability.
2. Apply Vendor Mitigations: Implement the specific corrective actions provided in the vendor’s instructions. This may involve firmware updates or configuration changes to the Redfish Host Interface.
3. Network Isolation: For systems where immediate patching is not feasible, restrict access to the BMC management network to trusted administrative hosts only. This limits the exposure path for spoofing attempts.
4. Decommissioning: If vendor mitigations are unavailable for a specific legacy version of the product, consider discontinuing use of the affected hardware or disabling the Redfish Host Interface if it is not required for operations.

How to validate remediation

Verification must go beyond checking a firmware version number, as version strings do not always confirm that a mitigation has been successfully applied and activated.

Defenders should verify remediation by following the specific validation steps outlined in the vendor’s security advisory. This may include confirming the application of a patch through a secure administrative console or testing the Redfish Host Interface against known spoofing vectors in a controlled, authorized environment to ensure the authentication bypass is no longer viable.

Limits and open questions

It remains unknown whether this vulnerability has been utilized in ransomware campaigns. Additionally, because MegaRAC SPx is integrated into various third-party products, there may be a delay between the availability of a fix from AMI and the release of an updated firmware package from the final hardware OEM. This creates a window of residual risk where the vulnerability is known but the specific hardware vendor has not yet provided the necessary update.

Source and editorial note

CVE-2024-54085: AMI MegaRAC SPx Authentication Bypass by Spoofing Vulnerability · Source date: June 25, 2025 · Retrieved August 31, 2026.

Material facts are tied to the cited primary source. Recommendations are independent defensive analysis unless attributed to the source. Confirm consequential decisions against current authoritative guidance.

Archive date: June 28, 2025. The displayed post date is assigned three days after the source date to organize this retrospective archive; it does not mean this site published the analysis then. First published by this site: October 10, 2026 at 00:31 UTC.

Request a Vulnerability Assessment