dbcve.org
Poweredge R660 FirmwareOperating system · Dell

CVE-2024-0172

HIGH · 7.8 CVSS v3.1 Published 2024-04-03
Fix available
A fix is available. Upgrade to 1.5.6 or later.
See remediation →
80/100
Remediation priority · High
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
Dell PowerEdge Server BIOS and Dell Precision Rack BIOS contain an improper privilege management security vulnerability. An unauthenticated local attacker could potentially exploit this vulnerability, leading to privilege escalation.

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 · moderate confidence

Dell PowerEdge Server BIOS and Dell Precision Rack BIOS contain an improper privilege management vulnerability that allows an unauthenticated local attacker to escalate privileges. The flaw exists in the BIOS privilege management mechanisms and can be exploited by someone with physical access to the affected system without requiring authentication.

MitigationApply the Dell BIOS/firmware update for CVE-2024-0172 to affected PowerEdge Server and Precision Rack systems. This requires downloading the updated BIOS from Dell's support site and updating via Dell Lifecycle Controller or equivalent firmware update mechanism.

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
Poweredge R660 FirmwareOperating system
Affected:< 1.5.6
Poweredge R760 FirmwareOperating system
Affected:< 1.5.6
Poweredge C6620 FirmwareOperating system
Affected:< 1.5.6
Poweredge Mx760c FirmwareOperating system
Affected:< 1.5.6
Poweredge R860 FirmwareOperating system
Affected:< 1.5.6
Poweredge R960 FirmwareOperating system
Affected:< 1.5.6
Poweredge Hs5610 FirmwareOperating system
Affected:< 1.5.6
Poweredge Hs5620 FirmwareOperating system
Affected:< 1.5.6

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 your PowerEdge model
    Check the system label on the chassis, or run 'dmidecode -s system-product-name' or access iDRAC web interface to confirm the exact model (R660, R760, C6620, Mx760c, R860, R960, Hs5610, or Hs5620)
    Affected if The model is any of the eight listed affected products
  2. Check the current BIOS/firmware version
    Access iDRAC and navigate to 'Overview > Server > Hardware > BIOS' or use the command 'racadm get BIOS.SysInformation.BiosVersion' via remote RACADM/SSH, or view BIOS version during boot (F2) or in BIOS setup utility under 'Main' or 'About'
    Affected if The firmware version cannot be determined or is not visible through these methods
  3. Compare your firmware version to 1.5.6
    Take the version number found in the previous step (for example 1.5.5, 1.4.2, etc.) and compare it numerically against 1.5.6 - note that versions like 1.5.5, 1.5.0, 1.4.10 are all less than 1.5.6
    Affected if Your installed BIOS/firmware version is less than 1.5.6 (for example: 1.5.5, 1.5.0, 1.4.8, etc.)

If you have a listed PowerEdge model (R660, R760, C6620, Mx760c, R860, R960, Hs5610, or Hs5620) and your BIOS/firmware version is below 1.5.6, your system is affected by this vulnerability.

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 1.5.6 or later
Fixed in 1.5.6
Interim mitigation

Apply the Dell BIOS/firmware update for CVE-2024-0172 to affected PowerEdge Server and Precision Rack systems. This requires downloading the updated BIOS from Dell's support site and updating via Dell Lifecycle Controller or equivalent firmware update mechanism.

Recommended fix High confidence

Firmware version 1.5.6 or later for affected PowerEdge models (R660, R760, C6620, Mx760c, R860, R960, Hs5610, Hs5620)

  1. Identify the specific PowerEdge model from the affected list (R660, R760, C6620, Mx760c, R860, R960, Hs5610, or Hs5620)
  2. Download the BIOS/firmware update package from Dell Support for your specific model (search Dell.com support for the model number and select "Drivers & Downloads")
  3. Extract the BIOS update file from the downloaded package
  4. Follow Dell's standard BIOS update procedure: typically run the .exe update utility from Windows/DOS or use the iDRAC Lifecycle Controller to apply the firmware update
  5. Reboot the server to complete the firmware update process
  6. Verify the firmware version has been updated to 1.5.6 or later using iDRAC or BIOS setup
Caveat BIOS firmware updates may require server downtime and should be planned during maintenance windows; always backup BIOS configuration before updating

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

Fix this in Poweredge R660 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,730
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0172 — 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-0172 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