CVE-2017-2108
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 · uneditedUntrusted search path vulnerability in PrimeDrive Desktop Application 1.4.3 and earlier allows remote attackers to gain privileges via a Trojan horse DLL in an unspecified directory.
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/untrusted search path vulnerability in PrimeDrive Desktop Application versions 1.4.3 and earlier. The application loads dynamic link libraries from directories that are not secured, allowing remote attackers to place a malicious Trojan horse DLL that gets loaded with elevated privileges when the application runs.
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<= 1.4.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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.
-
Identify if PrimeDrive Desktop Application is installedLook for PrimeDrive in the list of installed programs (Control Panel > Programs and Features on Windows, or check common installation directories such as C:\Program Files\PrimeDrive or C:\Program Files (x86)\PrimeDrive)Affected if PrimeDrive Desktop Application is present on the system
-
Determine the installed version of PrimeDriveRight-click the PrimeDrive executable, select Properties, and check the Version tab, or open the application and look for About/Help > Version informationAffected if The version is 1.4.3 or earlier
-
Inspect the permissions on the PrimeDrive installation directoryRight-click the PrimeDrive installation folder, select Properties > Security, and examine which users have Write or Modify permissionsAffected if Users other than administrators or the installing user have Write or Modify permissions to the directory
-
Check for unexpected DLL files in the PrimeDrive directoryOpen the PrimeDrive installation folder and look for DLL files that were not originally part of the application, especially those with recent modification dates or unfamiliar namesAffected if Unexpected DLL files are present in the installation directory
The system is affected if PrimeDrive Desktop Application version 1.4.3 or earlier is installed and running from a directory with weak permissions that allows other users to write files.
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 dataUsers should avoid running PrimeDrive from directories writable by other users, and consider alternative solutions or enhanced application controls until the vendor releases an updated version that implements secure DLL loading.
- Consultation2.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-2017-2108 — 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-2017-2108 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