dbcve.org
Xps 8960 FirmwareOperating system · Dell

CVE-2024-32858

HIGH · 8.2 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 1.14.0 / 1.16.0 or later.
See remediation →
84/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 Client Platform BIOS contains an Improper Input Validation vulnerability in an externally developed component. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Code execution.

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 Client Platform BIOS contains an Improper Input Validation vulnerability in an externally developed component. A high privileged attacker with local access to the system could exploit this vulnerability to achieve code execution, likely at BIOS/UEFI level privileges.

MitigationApply Dell BIOS/firmware updates when released; until then, restrict physical and local access to affected systems to trusted, high-privilege personnel only.

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
Xps 8960 FirmwareOperating system
Affected:< 2.6.0
Xps 8950 FirmwareOperating system
Affected:< 1.19.0
Inspiron 3502 FirmwareOperating system
Affected:< 1.16.0
Inspiron 15 3521 FirmwareOperating system
Affected:< 1.14.0
Inspiron 15 3510 FirmwareOperating system
Affected:< 1.19.0
Aurora R16 FirmwareOperating system
Affected:< 2.7.0
Alienware X17 R2 FirmwareOperating system
Affected:< 1.20.0
Alienware X17 R1 FirmwareOperating system
Affected:< 1.22.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
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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 the Dell system model
    Run 'dmidecode -s system-product-name' or check the product label on the chassis or in BIOS setup under System Information
    Affected if Model is one of: XPS 8960, XPS 8950, Inspiron 3502, Inspiron 15 3521, Inspiron 15 3510, Aurora R16, Alienware X17 R2, or Alienware X17 R1
  2. Retrieve the current BIOS firmware version
    Run 'dmidecode -s bios-version' or check in BIOS setup under BIOS Version / BIOS Update
    Affected if Unable to retrieve version or version displays as unknown
  3. Compare XPS 8960 firmware version
    If system is XPS 8960, compare your installed version against 2.6.0
    Affected if Installed version is below 2.6.0
  4. Compare XPS 8950 firmware version
    If system is XPS 8950, compare your installed version against 1.19.0
    Affected if Installed version is below 1.19.0
  5. Compare Inspiron firmware versions
    If system is Inspiron 3502, compare against 1.16.0; if Inspiron 15 3521, compare against 1.14.0; if Inspiron 15 3510, compare against 1.19.0
    Affected if Installed version is below the respective threshold for that model
  6. Compare Aurora and Alienware firmware versions
    If system is Aurora R16, compare against 2.7.0; Alienware X17 R2 compare against 1.20.0; Alienware X17 R1 compare against 1.22.0
    Affected if Installed version is below the respective threshold for that model

The system is affected if it matches any listed Dell model AND its current BIOS/firmware version is below the version threshold specified for that model.

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.14.0 / 1.16.0 / 1.19.0 or later
Fixed in 1.14.01.16.01.19.0
Interim mitigation

Apply Dell BIOS/firmware updates when released; until then, restrict physical and local access to affected systems to trusted, high-privilege personnel only.

Recommended fix High confidence

Dell BIOS/firmware version 2.6.0 (Xps 8960), 1.19.0 (Xps 8950/Inspiron 15 3510), 1.16.0 (Inspiron 3502), 1.14.0 (Inspiron 15 3521), 2.7.0 (Aurora R16), 1.20.0 (Alienware X17 R2), 1.22.0 (Alienware X17 R1)

  1. 1. Identify the exact Dell system model by checking the system service tag or model number on the device
  2. 2. Navigate to Dell's support website (www.dell.com) and enter the service tag or model to find the appropriate BIOS/firmware update
  3. 3. Download the BIOS update file corresponding to the fixed version for your specific model (Xps 8960: 2.6.0, Xps 8950: 1.19.0, Inspiron 3502: 1.16.0, Inspiron 15 3521: 1.14.0, Inspiron 15 3510: 1.19.0, Aurora R16: 2.7.0, Alienware X17 R2: 1.20.0, Alienware X17 R1: 1.22.0)
  4. 4. Review the BIOS update release notes for any prerequisites or special instructions
  5. 5. Connect the system to AC power to ensure uninterrupted firmware update process
  6. 6. Run the Dell BIOS update executable or use the Dell Update Package (DUP) to apply the firmware update
  7. 7. Allow the system to complete the update and restart - do not interrupt the process
  8. 8. Verify the BIOS version has been updated to the fixed release version after restart
Caveat BIOS updates carry risk of system damage if interrupted; ensure stable power and do not interrupt the update process

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

Fix this in Xps 8960 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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