dbcve.org
Idrac9Application · Dell

CVE-2024-25943

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-29
Fix available
A fix is available. Upgrade to 7.00.00.172 / 7.10.50.00 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
iDRAC9, versions prior to 7.00.00.172 for 14th Generation and 7.10.50.00 for 15th and 16th Generations, contains a session hijacking vulnerability in IPMI. A remote attacker could potentially exploit this vulnerability, leading to arbitrary code execution on the vulnerable application.

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 confidence

iDRAC9 contains a session hijacking vulnerability in its IPMI subsystem affecting versions prior to 7.00.00.172 (14th Gen) and 7.10.50.00 (15th/16th Gen). A remote attacker can hijack IPMI sessions, potentially leading to arbitrary code execution on the vulnerable system.

MitigationUpdate iDRAC9 firmware to version 7.00.00.172 or later for 14th Generation, or 7.10.50.00 or later for 15th and 16th Generations.

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
Idrac9Application
Affected:< 7.00.00.172< 7.10.50.00

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify iDRAC9 generation
    Check the server model or use racadm: racadm get SystemInfo.4.1#System.8.1#Model or inspect the physical server label for Generation (14th, 15th, or 16th)
    Affected if Generation is indeterminate but iDRAC9 is present
  2. Determine iDRAC9 firmware version via racadm
    Run: racadm get idrac.Info | grep -i Version or racadm fwversion
    Affected if Version is below 7.00.00.172 for 14th Gen, or below 7.10.50.00 for 15th/16th Gen
  3. Determine iDRAC9 firmware version via Redfish API
    Send GET to https://<idrac-ip>/redfish/v1/Managers/iDRAC.Embedded.1 and check FirmwareVersion in the response
    Affected if Version is below 7.00.00.172 for 14th Gen, or below 7.10.50.00 for 15th/16th Gen
  4. Verify IPMI over LAN is enabled
    Run: racadm get iDRAC.IPMI.1.1#IPMILan.1.1#Enable or use IPMI: ipmitool -I lanplus -H <idrac-ip> -U <user> lan print 1 and check 'IPMI Lan Enable'
    Affected if IPMI over LAN is enabled (vulnerability requires IPMI subsystem access)

User is affected if iDRAC9 firmware version is below 7.00.00.172 (14th Gen) or below 7.10.50.00 (15th/16th Gen) AND IPMI over LAN is enabled on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.00.00.172 / 7.10.50.00 or later
Fixed in 7.00.00.1727.10.50.00
Interim mitigation

Update iDRAC9 firmware to version 7.00.00.172 or later for 14th Generation, or 7.10.50.00 or later for 15th and 16th Generations.

Recommended fix High confidence

iDRAC9 7.00.00.172 (14th Gen) or 7.10.50.00 (15th/16th Gen)

  1. Identify your iDRAC9 version by checking the iDRAC web interface or using RACADM: racadm get iDRAC.WebServer.1.Timeout
  2. Determine your server generation (14th, 15th, or 16th Gen)
  3. Download the appropriate iDRAC firmware from Dell Support: Go to dell.com/support, enter your service tag, select Drivers & Downloads, find iDRAC firmware
  4. For 14th Generation servers: Download iDRAC9 firmware version 7.00.00.172 or later
  5. For 15th and 16th Generation servers: Download iDRAC9 firmware version 7.10.50.00 or later
  6. Upload the firmware via iDRAC web interface: iDRAC Settings > Maintenance > Firmware Update > Manual Update, or use RACADM: racadm update -f <firmware_file>.exe
  7. Wait for firmware upload and installation to complete (do not interrupt power)
  8. Verify the upgrade was successful by checking iDRAC version: racadm get iDRAC.Info
Caveat Firmware updates may require downtime; verify compatibility with your specific Dell PowerEdge server model before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Idrac9 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25943 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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