# CVE-2019-3726: Other in Dell Client Platforms: Dell Update Packages (DUP) Framework file

> A local attacker can execute arbitrary code with administrator privileges by tricking an admin into running a trusted binary that loads a malicious DLL via an uncontrolled search path.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c3v3-2rrj-72gc

## What is CVE-2019-3726?

CVE-2019-3726 is a medium-severity vulnerability in Dell Client Platforms: Dell Update Packages (DUP) Framework file, published on 24 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An Uncontrolled Search Path Vulnerability is applicable to the following: Dell Update Package (DUP) Framework file versions prior to 19.1.0.413, and Framework file versions prior to 103.4.6.69 used in Dell EMC Servers. Dell Update Package (DUP) Framework file versions prior to 3.8.3.67 used in Dell Client Platforms. The vulnerability is limited to the DUP framework during the time window when a DUP is being executed by an administrator. During this time window, a locally authenticated low privilege malicious user potentially could exploit this vulnerability by tricking an administrator into running a trusted binary, causing it to load a malicious DLL and allowing the attacker to execute arbitrary code on the victim system. The vulnerability does not affect the actual binary payload that the DUP delivers.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Dell Update Package Framework.

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

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

## Is CVE-2019-3726 being exploited?

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

## Other vulnerabilities in Dell Client Platforms: Dell Update Packages (DUP) Framework file

- [CVE-2026-71180](https://insights.sbomify.com/CVE-2026-71180/): Privilege escalation in Update Package Framework (high 8.2)
- [CVE-2026-23857](https://insights.sbomify.com/CVE-2026-23857/): Privilege escalation in Update Package (high 8.2)
- [CVE-2025-22395](https://insights.sbomify.com/CVE-2025-22395/): Privilege escalation in Dell Update Package (DUP) Framework (high 8.2)
- [CVE-2026-71179](https://insights.sbomify.com/CVE-2026-71179/): Command injection in Update Package Framework (high 7.3)
- [CVE-2023-39254](https://insights.sbomify.com/CVE-2023-39254/): Path traversal in DUP Framework (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3726 is a medium-severity vulnerability in Dell Client Platforms: Dell Update Packages (DUP) Framework file, published on 24 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-3726 in the wild and no public exploit code.

Affected product: Dell Client Platforms: Dell Update Packages (DUP) Framework file. 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-3726/ (Markdown: https://insights.sbomify.com/CVE-2019-3726/index.md)
```

## Sources

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

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