CVE-2018-8714
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 · uneditedHoneywell MatrikonOPC OPC Controller before 5.1.0.0 allows local users to transfer arbitrary files from a host computer and consequently obtain sensitive information via vectors related to MSXML libraries.
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 confidenceMatrikonOPC OPC Controller before version 5.1.0.0 contains a vulnerability allowing local users to transfer arbitrary files from the host system. The issue stems from improper handling or validation within MSXML library interactions, enabling unauthorized file access and exfiltration of sensitive data.
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< 5.1.0.0CVSS 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
- None
- Availability
- Low
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
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 installed MatrikonOPC Explorer versionOpen Windows Control Panel > Programs and Features, or check the application About/Help dialog to locate the installed version number of MatrikonOPC Explorer.Affected if The installed version is lower than 5.1.0.0 (for example, 4.x, 5.0.x, or any version number below 5.1.0.0).
-
Confirm application uses MSXML functionalityReview application logs or documentation to determine if the MatrikonOPC Explorer installation interacts with MSXML libraries for XML parsing or data handling.Affected if The application uses MSXML library interactions for OPC data exchange, which is standard operation for this product.
-
Verify local user account privilegesCheck Windows Local Users and Groups (lusrmgr.msc) or use 'net user' command to enumerate local user accounts that have access to the system where MatrikonOPC is installed.Affected if Multiple local user accounts exist on the system with file system access permissions.
-
Inspect file transfer capabilitiesReview application configuration files (typically in the installation directory) or logs for settings related to file transfer, XML import/export, or data staging features.Affected if File transfer or XML import/export features are enabled in the application configuration.
You are affected if MatrikonOPC Explorer version is below 5.1.0.0 and the application processes XML data via MSXML, allowing local authenticated users to potentially access files outside intended directories.
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 data5.1.0.0
Upgrade MatrikonOPC OPC Controller to version 5.1.0.0 or later. Apply least-privilege principles to restrict local user file system access and audit user permissions.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8714 — 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-8714 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