Threats / AMI / CVE-2024-54085
CVE-2024-54085
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
AMI MegaRAC SPx vulnerability
AMI MegaRAC SPx contains an authentication bypass vulnerability in the Redfish Host Interface that allows attackers to spoof credentials and gain unauthorized access, potentially compromising confidentiality, integrity, and availability.
Verdict
Today item — known-exploited.
An unauthenticated attacker can bypass authentication controls on the Redfish Host Interface through credential spoofing, gaining unauthorized administrative access to the baseboard management controller and its managed systems.
CISA KEV Yes · 2025-06-255EPSS 0.60747 (verify live)6Exploit Weaponized · public PoC7CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-06-25).
Probability (EPSS)
EPSS 0.60747 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H) · Affected: AMI, MegaRAC SPx. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-290 Auth Bypass by Spoofing — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 106 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a spoofed authentication request to the Redfish Host Interface without valid credentials.
Business
Attacker gains unauthorized access to the baseboard management controller, bypassing security perimeter controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I assume administrative privileges over the managed server and its firmware components.
Business
Attacker can modify system configurations, disable security features, or inject malicious code at the firmware level.
3
Lateral reach — past segmentation narrative 3
Attacker
I exfiltrate sensitive data from the managed system or establish persistent backdoor access.
Business
Organization suffers data breach, loss of system availability, and compromised infrastructure integrity across the data center.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by AMICNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.