CVE-2018-0667
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 Installer of INplc SDK Express 3.08 and earlier and Installer of INplc SDK Pro+ 3.08 and earlier allows an attacker 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 search path hijacking vulnerability in the INplc SDK installers (versions 3.08 and earlier for both Express and Pro+ editions). The installer loads DLLs from insecure locations, allowing an attacker to place a malicious Trojan horse DLL in an unspecified directory that gets loaded before the legitimate DLL, resulting in privilege escalation.
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.08<= 3.08CVSS 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.
-
Locate INplc SDK installer filesSearch the file system for installer executables named similarly to 'INplc*SDK*Installer*.exe' or 'MncInplc*Sdk*Setup*.exe' in typical download directories, software deployment shares, and installation media locationsAffected if any installer file matching the INplc SDK Express or Pro+ product line is found on the system
-
Identify installer versionRight-click the found installer file, select Properties, and examine the Version tab for the product version. Alternatively, run 'strings' or a hex editor on the executable to locate embedded version metadataAffected if the displayed version is 3.08 or lower, or the version cannot be determined and the file appears to be an older INplc SDK installer
-
Confirm product editionExamine the installer filename and version information to determine if it corresponds to 'Mnc Inplc Rt Sdk Express' or 'Mnc Inplc Sdk Pro+'Affected if the installer is confirmed as either the Express edition or Pro+ edition and meets the version criteria in step 2
-
Assess execution contextReview system logs, installer cache directories (such as %TEMP% or %USERPROFILE%\AppData\Local\Temp), and software distribution folders for recent INplc SDK installation activityAffected if evidence shows the vulnerable installer has been executed recently or resides in a directory from which users commonly run installations
If an INplc SDK installer version 3.08 or earlier for Express or Pro+ editions is present or has been executed on the system, the environment is affected by this DLL search path hijacking vulnerability.
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 the vulnerable installer versions and wait for an official patch from the vendor. If the installer must be used, ensure no untrusted executables or DLLs exist in any directory the installer may search, and consider running in a sandboxed environment.
- 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-2018-0667 — 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-2018-0667 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