CVE-2017-2175
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 Empirical Project Monitor - eXtended all versions 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 · moderate confidenceThis is a DLL hijacking vulnerability (untrusted search path) in Empirical Project Monitor - eXtended. The application uses an insecure search path to locate DLL files, allowing attackers to place a malicious Trojan horse DLL in a directory that the application searches. When the application runs, it loads the attacker's DLL instead of the legitimate one, executing arbitrary code with the application's privileges.
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 dataall versionsCVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/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.
-
Verify Ipa Empirical Project Monitor Extended is installedCheck for the application in standard installation directories (typically C:\Program Files\ or C:\Program Files (x86)\) or search for files named 'Empirical Project Monitor' or 'EPM' on the systemAffected if The application is present on the system
-
Identify the application's DLL search pathUse a process monitor tool or examine the application's configuration files and startup behavior to determine which directories it searches when loading DLLsAffected if The application searches multiple directories for DLLs without using absolute paths
-
Check for writable directories in the DLL search pathReview each directory in the application's DLL search path and verify write permissions for standard users or low-privileged accountsAffected if Any directory in the search path is writable by an untrusted user
-
Inspect search path directories for suspicious DLLsList all DLL files in directories within the application's search path and compare against known legitimate DLLs expected by the applicationAffected if Unexpected or unknown DLL files exist in directories the application searches for DLL loading
If Ipa Empirical Project Monitor Extended is installed and any directory in its DLL search path is writable by an untrusted user, the environment is vulnerable to CVE-2017-2175.
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 dataRemove or secure any writable directories in the application's DLL search path, implement secure DLL loading using absolute paths or explicit paths, and verify that the application only loads DLLs from trusted locations.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2175 — 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-2175 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