CVE-2018-7687
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 · uneditedThe Micro Focus Client for OES before version 2 SP4 IR8a has a vulnerability that could allow a local attacker to elevate privileges via a buffer overflow in ncfsd.sys.
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 confidenceA buffer overflow vulnerability in the ncfsd.sys kernel driver of Micro Focus Client for OES allows a local attacker to execute arbitrary code with elevated privileges. The flaw exists in versions prior to 2 SP4 IR8a.
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<= 2.0= 2.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
- 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.
-
Verify Micro Focus Client for OES is installedCheck the installed programs list in Windows Control Panel or use 'wmic product' to list installed software and look for 'Micro Focus Client for OES' or 'Microfocus Client'Affected if The software is not found in the installed programs list, then it is not affected (unless manually installed elsewhere)
-
Identify installed version of Micro Focus Client for OESLocate the product in the installed programs list and note the version displayed, or use registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to find the version stringAffected if The displayed version is 2.0 or any version lower than 2.0 (such as 1.x)
-
Locate and check ncfsd.sys driver versionSearch for ncfsd.sys in the Micro Focus Client installation directory (commonly under C:\Program Files\Micro Focus or C:\Program Files (x86)\Micro Focus) and right-click the file to view Properties > Details for the File VersionAffected if The ncfsd.sys file exists and its version is 2.0. IR8a or earlier, or if the file version cannot be determined to be later than 2 SP4 IR8a
-
Compare against affected version rangeCompare the installed version of the client and the ncfsd.sys driver version against the affected range (<=2.0 or =2.0) and the fixed version (2 SP4 IR8a)Affected if Either the client version or the driver version is 2.0 or earlier, or the version is unknown but older than 2 SP4 IR8a
You are affected if Micro Focus Client for OES is installed with version 2.0 or earlier, or if the ncfsd.sys driver version cannot be confirmed as later than 2 SP4 IR8a.
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 dataUpgrade Micro Focus Client for OES to version 2 SP4 IR8a or later to remediate the buffer overflow vulnerability.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7687 — 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-7687 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