basicsecurity.net
Proof, not just disclosure.
Threats / AMI / CVE-2024-54085
CVE-2024-54085 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-253EPSS 0.61202 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.61202 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: AMI, MegaRAC SPx. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-290 Auth Bypass by Spoofing — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 6 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by AMI (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by AMICNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.