CVE-2018-20029
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 nxfs.sys driver in the DokanFS library 0.6.0 in NoMachine before 6.4.6 on Windows 10 allows local users to cause a denial of service (BSOD) because uninitialized memory can be read.
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 confidenceThe nxfs.sys kernel driver in DokanFS library 0.6.0 (used by NoMachine before 6.4.6 on Windows 10) contains a flaw where uninitialized memory is read before use, causing a kernel panic (BSOD) when triggered by local users. This is a denial-of-service vulnerability stemming from improper memory initialization in the file system driver.
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= 0.6.0< 6.4.6CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Check installed Dokany versionOpen Windows Control Panel > Programs and Features, look for 'Dokan Dev Dokany' or check the installed files in the Dokany installation directory for version information, typically found in the program's main folder or readme filesAffected if The installed version is exactly 0.6.0 (Dokan Dev Dokany = 0.6.0)
-
Check installed NoMachine versionOpen NoMachine, go to the main menu and select 'About' or check in Windows Control Panel > Programs and Features for 'Nomachine Nomachine' entry which displays the version numberAffected if The installed NoMachine version is less than 6.4.6 (any version before 6.4.6)
-
Locate and verify nxfs.sys driverSearch for the file nxfs.sys in the NoMachine installation directory (commonly in C:\Program Files\Nomachine\bin\ or C:\Program Files\Nomachine\nxs\), right-click the file and select Properties > Details to view version informationAffected if The nxfs.sys driver exists and originates from the vulnerable DokanFS library version 0.6.0 used by NoMachine versions before 6.4.6
-
Confirm Windows 10 environmentType 'winver' in Windows Run dialog or check System Properties to identify the Windows versionAffected if Running Windows 10 (the advisory specifically notes this vulnerability affects NoMachine on Windows 10)
You are affected if you have Dokan Dev Dokany version 0.6.0 or NoMachine version less than 6.4.6 running on Windows 10 with the vulnerable nxfs.sys driver present.
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 data6.4.6
Upgrade NoMachine to version 6.4.6 or later which contains the patched DokanFS library, or apply any vendor-supplied updates to the nxfs.sys driver to resolve the uninitialized memory read issue.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20029 — 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-20029 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