# CVE-2019-18579: Settings for the Dell XPS 13 2-in-1 (7390) BIOS versions prior to 1.1.3 contain a configuration vulnerability.


- **Severity:** High 7.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 Dec 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3fj2-qcp9-8293

## What is CVE-2019-18579?

CVE-2019-18579 is a high-severity vulnerability in Dell CPG BIOS, published on 16 Dec 2019. 

### Official description

Settings for the Dell XPS 13 2-in-1 (7390) BIOS versions prior to 1.1.3 contain a configuration vulnerability. The BIOS configuration for the "Enable Thunderbolt (and PCIe behind TBT) pre-boot modules" setting is enabled by default. A local unauthenticated attacker with physical access to a user's system can obtain read or write access to main memory via a DMA attack during platform boot.

Weakness: CWE-16

## Which versions are affected by CVE-2019-18579?

It affects 1 product.


Products: Dell Xps 7390 Firmware.

## How do I fix CVE-2019-18579?

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

## Is CVE-2019-18579 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18579 and fix it if it is affected.

What it is: CVE-2019-18579 is a high-severity vulnerability in Dell CPG BIOS, published on 16 Dec 2019. 
Exploitation: There is no known exploitation of CVE-2019-18579 in the wild and no public exploit code.

Affected product: Dell CPG 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-2019-18579/ (Markdown: https://insights.sbomify.com/CVE-2019-18579/index.md)
```

## Sources

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

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