dbcve.org
Poweredge R660 FirmwareOperating system · Dell

CVE-2024-0163

MEDIUM · 6.3 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 1.8.0 / 2.0.0 or later.
See remediation →
65/100
Remediation priority · Elevated
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 a TOCTOU race condition vulnerability. A local low privileged attacker could potentially exploit this vulnerability to gain access to otherwise unauthorized resources.

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

A Time-of-Check-Time-of-Use (TOCTOU) race condition vulnerability exists in Dell PowerEdge Server BIOS and Dell Precision Rack BIOS firmware. A local low-privileged attacker could potentially exploit the race window between security checks and resource access to bypass authorization controls and gain access to otherwise restricted resources.

MitigationApply the Dell-supplied BIOS/firmware update for your specific PowerEdge or Precision Rack model. Organizations should prioritize patching given the local attack vector and the high-impact nature of BIOS-level compromise.

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

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

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 server model via the physical chassis label, iDRAC web interface (System > Overview), or by running `racadm getsysinfo` or `omreport chassis info`
    Affected if The model is one of: R660, R760, C6620, Mx760c, R860, R960, Hs5610, or Hs5620
  2. Retrieve the current BIOS firmware version
    Access the BIOS version through iDRAC (Maintenance > System Update > Firmware Inventory), or use `racadm get BIOS.SysInformation` or check the BIOS setup screen under Main > BIOS Version
    Affected if A version is successfully retrieved that can be compared against the affected ranges
  3. Compare the installed version against affected thresholds
    For R660, R760, C6620, Mx760c, Hs5610, Hs5620: check if version is less than 2.0.0. For R860, R960: check if version is less than 1.8.0. Use the version shown in iDRAC or BIOS
    Affected if The installed BIOS version is below 2.0.0 for R660/R760/C6620/Mx760c/Hs5610/Hs5620, or below 1.8.0 for R860/R960
  4. Verify iDRAC firmware version is current
    In iDRAC, go to Maintenance > System Update > Firmware Inventory to list all firmware components. Confirm iDRAC itself is not outdated, as iDRAC provides the version reporting interface
    Affected if iDRAC cannot be reached or does not return version information, making BIOS version verification unreliable

You are affected if you run a listed PowerEdge model (R660, R760, C6620, Mx760c, R860, R960, Hs5610, Hs5620) and your BIOS firmware version is below 2.0.0 (for R660/R760/C6620/Mx760c/Hs5610/Hs5620) or below 1.8.0 (for R860/R960).

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.8.0 / 2.0.0 or later
Fixed in 1.8.02.0.0
Interim mitigation

Apply the Dell-supplied BIOS/firmware update for your specific PowerEdge or Precision Rack model. Organizations should prioritize patching given the local attack vector and the high-impact nature of BIOS-level compromise.

Recommended fix High confidence

PowerEdge R660/R760/C6620/Mx760c/Hs5610/Hs5620: BIOS Firmware 2.0.0 | PowerEdge R860/R960: BIOS Firmware 1.8.0

  1. 1. Identify the specific PowerEdge model from the affected list (R660, R760, C6620, Mx760c, R860, R960, Hs5610, or Hs5620)
  2. 2. Download the latest BIOS/firmware update from Dell's support website for your specific model
  3. 3. Review the BIOS update release notes to confirm the version addresses CVE-2024-0163
  4. 4. Back up current BIOS configuration if applicable
  5. 5. Apply the BIOS/firmware update using Dell's update utility (e.g., iDRAC Lifecycle Controller, Dell Update Package, or BIOS setup menu)
  6. 6. Reboot the server to complete the firmware update process
  7. 7. Verify the BIOS version has been updated to the fixed release (2.0.0 for R660/R760/C6620/Mx760c/Hs5610/Hs5620, or 1.8.0 for R860/R960)
Caveat Firmware updates on production servers may require planned downtime; ensure proper backup and testing procedures are followed

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

Fix this in Poweredge R660 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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