# CVE-2024-42424: Information disclosure in Dell Precision Rack BIOS

> A local high-privileged attacker can exploit improper input validation in Dell Precision Rack BIOS to disclose sensitive information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2024
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-6fx3-92c8-8qcg

## What is CVE-2024-42424?

CVE-2024-42424 is a medium-severity vulnerability in Dell Precision Rack BIOS, published on 10 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dell Precision Rack, 14G Intel BIOS versions prior to 2.22.2, contains an Improper Input Validation vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Information disclosure.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-42424?

It affects 2 products.


Products: Dell 7920 Xl Rack Firmware, Dell Precision 7920 Rack Firmware.

## How do I fix CVE-2024-42424?

No fix has been published for CVE-2024-42424 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-42424 being exploited?

There is no known exploitation of CVE-2024-42424 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42424 and fix it if it is affected.

What it is: CVE-2024-42424 is a medium-severity vulnerability in Dell Precision Rack BIOS, published on 10 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42424 in the wild and no public exploit code.

Affected product: Dell Precision Rack BIOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-42424/ (Markdown: https://insights.sbomify.com/CVE-2024-42424/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42424
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42424
- OSV: https://osv.dev/vulnerability/CVE-2024-42424

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-42424/
Summaries are generated and may contain mistakes; the official description above is the record.