CVE-2019-3726
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 · uneditedAn 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.
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 · high confidenceThis is a DLL hijacking/uncontrolled search path vulnerability in Dell Update Package (DUP) Framework. When an administrator executes a DUP, the framework may load DLLs from an unsecured search path, allowing a locally authenticated low-privilege attacker to place a malicious DLL that gets loaded by the trusted binary, resulting in arbitrary code execution with administrator privileges during the update window.
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< 3.8.3.67< 103.4.6.69< 19.1.0.413CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Dell Update Package Framework is installedLook for Dell Update Package Framework components on the system. On Windows, check Program Files for Dell folders or check for DellUpdate.exe or related DUP executables.Affected if Dell DUP Framework is present on the system
-
Identify the installed DUP Framework versionLocate the main DUP Framework executable or DLL (typically named DellUpdate.exe, DupFramework.dll, or similar) and view its file properties to find the version number.Affected if The version number is lower than 3.8.3.67, 103.4.6.69, or 19.1.0.413 depending on the platform type
-
Determine the platform type of the installationIdentify whether the Dell system is a Client Platform, Server, or Dell EMC Server to match the correct version threshold (Client: 3.8.3.67, Servers: 103.4.6.69, Dell EMC: 19.1.0.413).Affected if The installed version falls below the threshold for its platform type
-
Check the DUP execution directory for writable locationsIdentify the typical directory from which DUP updates are launched and verify if any subdirectories or locations in that path are writable by low-privilege users.Affected if The directory from which DUPs are run or any location in the DLL search path is writable by non-admin users
If Dell DUP Framework is installed and its version is below the platform-specific threshold (3.8.3.67, 103.4.6.69, or 19.1.0.413) and the execution directory is writable by low-privilege users, the system is vulnerable to DLL hijacking.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data3.8.3.6719.1.0.413103.4.6.69
Update Dell DUP Framework to version 19.1.0.413 or later (Dell EMC Servers), 103.4.6.69 or later (Servers), or 3.8.3.67 or later (Dell Client Platforms). As a temporary workaround, ensure the directory from which DUPs are run does not contain any attacker-writable locations.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3726 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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