CVE-2024-54085
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAMI’s SPx contains a vulnerability in the BMC where an Attacker may bypass authentication remotely through the Redfish Host Interface. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAMI SPx BMC firmware contains an authentication bypass vulnerability in the Redfish Host Interface that allows remote attackers to bypass authentication and gain unauthorized access to the BMC management functions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 12, < 12.7>= 13, < 13.5all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify BMC firmware vendor and versionAccess BMC web interface or use IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw command to get firmware version, or check via Redfish API endpoint /redfish/v1/Managers/1 and look for FirmwareVersion or BiosVersion fieldsAffected if The firmware version matches Ami Megarac Sp X versions 12.x where x < 7, or 13.x where x < 5, indicating an unpatched vulnerable version
-
Confirm Redfish Host Interface is enabledCheck BMC configuration for Redfish Host Interface settings, typically found in BMC web UI under 'Services' or 'Redfish' settings, or query /redfish/v1/Managers/1/NetworkProtocolAffected if Redfish Host Interface is enabled and accessible over network, making the authentication bypass exploitable
-
For NetApp systems, identify the specific hardware modelCheck NetApp H-series or SG-series appliance model via physical label, BMC interface, or /redfish/v1/Systems/1 endpointAffected if System is one of NetApp H300s, H500s, H700s, H410s, H410c, Sg6160, or Sgf6112 with any firmware version, as all versions of these models are affected
-
Verify network exposure of BMC Redfish serviceScan network for accessible Redfish ports (typically 443 or 4433 with /redfish path) using nmap -p 443,4433 --script=redfish-get-version <BMC_IP> or curl https://<BMC_IP>/redfish/v1Affected if BMC Redfish interface is exposed to untrusted networks without proper network segmentation, increasing exploitability
You are affected if your BMC runs Ami Megarac Sp X firmware versions 12.x < 12.7 or 13.x < 13.5, or is any NetApp H300s/H500s/H700s/H410s/H410c/Sg6160/Sgf6112 model, and the Redfish Host Interface is enabled and accessible on your network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped12.713.5
Apply vendor-supplied firmware patches for SPx BMC when available; restrict Redfish interface network access and monitor for unauthorized access attempts until patch can be deployed.
Megarac Sp X 12.7 or later; Megarac Sp X 13.5 or later
- 1. Identify the exact Megarac SPx version running on the BMC by accessing the BMC web interface or using Redfish API to query /api/manager/v1/Managers/1
- 2. For Megarac Sp X versions 12.x: Upgrade to version 12.7 or later
- 3. For Megarac Sp X versions 13.x: Upgrade to version 13.5 or later
- 4. For H300s, H500s, H700s, H410s, H410c, Sg6160, and Sgf6112 firmware: Contact AMI (American Megatrends) or the original equipment manufacturer (OEM) for patched firmware as no fixed version is publicly specified for these models
- 5. After upgrading, verify the BMC firmware version matches the fixed release
- 6. Test Redfish Host Interface authentication to confirm the fix is effective
- 7. Review and monitor BMC access logs for any signs of exploitation attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54085 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54085 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data