dbcve.org
Windows 10Operating system · Microsoft

CVE-2016-3343

HIGH · 7.8 CVSS v3.0 Published 2016-11-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
The Common Log File System (CLFS) driver in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, and 1607, and Windows Server 2016 allows local users to gain privileges via a crafted application, aka "Windows Common Log File System Driver Elevation of Privilege Vulnerability," a different vulnerability than CVE-2016-0026, CVE-2016-3332, CVE-2016-3333, CVE-2016-3334, CVE-2016-3335, CVE-2016-3338, CVE-2016-3340, CVE-2016-3342, and CVE-2016-7184.

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 confidence

A local privilege escalation vulnerability in the Windows Common Log File System (CLFS) driver allows authenticated local users to execute arbitrary code with elevated SYSTEM privileges by running a specially crafted application that exploits the kernel-mode driver.

MitigationApply the Microsoft security update for CVE-2016-3343 (MS16-111) to all affected Windows systems. This patches the CLFS.sys driver to properly validate input and prevent 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
Windows 10Operating system
Affected:all versions= 1511= 1607
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions
Windows VistaOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Windows version is in affected range
    Run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to identify the Windows version. Check against the list: Windows 10 (all, 1511, 1607), Windows 7 (all), Windows 8.1 (all), Windows Rt 8.1 (all), Windows Server 2008 (all, R2), Windows Server 2012 (all, R2), Windows Server 2016 (all), Windows Vista (all).
    Affected if The installed Windows version matches any of the affected versions listed in the CVE details.
  2. Locate and identify CLFS driver file version
    Check the file version of clfs.sys at C:\Windows\System32\clfs.sys by right-clicking the file, selecting Properties, and viewing the Details tab, or using `dir C:\Windows\System32\clfs.sys /Q` and then inspecting the file version through PowerShell with `(Get-Item C:\Windows\System32\clfs.sys).VersionInfo`.
    Affected if The CLFS driver exists on the system (present by default on affected Windows versions).
  3. Compare CLFS driver version to known patched version
    Note the File Version shown (format such as x.x.x.x). Compare this version number against the version released with Microsoft security update MS16-111. The patched version varies by Windows version; compare your installed version against the affected (vulnerable) version range for your specific Windows release.
    Affected if The clfs.sys file version is lower than the version released with MS16-111 for your specific Windows build, indicating the security update has not been applied.
  4. Verify MS16-111 security update is installed
    Run `Get-HotFix -ID "KB3186973"` in PowerShell or use `systeminfo | findstr "Hotfix"` to list installed updates. Alternatively, check Windows Update history for security update KB3186973.
    Affected if The security update KB3186973 (MS16-111) is NOT listed among installed hotfixes, meaning the CLFS vulnerability remains unpatched.

The system is vulnerable if it runs an affected Windows version AND the CLFS driver is present AND the MS16-111 security update (KB3186973) has not been installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update for CVE-2016-3343 (MS16-111) to all affected Windows systems. This patches the CLFS.sys driver to properly validate input and prevent privilege escalation.

Fix this in Windows 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-3343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-3343 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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