CVE-2018-0671
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 · uneditedPrivilege escalation vulnerability in INplc-RT 3.08 and earlier allows an attacker with administrator rights to execute arbitrary code on the Windows system via unspecified vectors.
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 local privilege escalation vulnerability in INplc-RT, an industrial PLC runtime system for Windows. An attacker who already possesses administrator-level credentials can exploit unspecified vectors to execute arbitrary code with elevated system privileges beyond the intended administrator scope.
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.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/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.
-
Verify INplc-RT installationSearch for INplc-RT components on the system. Check common installation directories such as C:\Program Files\INplc or C:\Program Files (x86)\INplc, and look for service entries in Windows Services (services.msc) named INplc or Mnc Inplc.Affected if INplc-RT or Mnc Inplc Rt is found installed on the system.
-
Determine installed versionLocate the INplc-RT executable or DLL files (typically in the installation directory) and check file properties for version information, or use the Windows registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Mnc or the installed program's uninstall entry.Affected if The installed version is 3.08 or any version lower than 3.08.
-
Confirm service configurationOpen Services (services.msc), find the INplc-RT service, right-click and select Properties, and examine the 'Log on as' field to determine the service account.Affected if The service runs under the LocalSystem account or another system-level account with elevated privileges.
-
Assess local administrator accessUse 'net localgroup Administrators' or check Group Policy settings to list all accounts granted administrator-level access on the affected machine.Affected if Multiple accounts or groups have administrator-level access beyond the trusted personnel who require it.
The system is affected if INplc-RT (Mnc Inplc Rt) version 3.08 or lower is installed and its service runs with system-level privileges, allowing a local administrator to escalate beyond their intended scope.
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 dataRestrict administrator access to trusted personnel only, investigate if a patched version of INplc-RT exists beyond 3.08, and apply the principle of least privilege to limit the attack surface for privilege escalation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0671 — 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-0671 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