dbcve.org
Windows 10Operating system · Microsoft

CVE-2018-1040

MEDIUM · 5.3 CVSS v3.0 Published 2018-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
A denial of service vulnerability exists in the way that the Windows Code Integrity Module performs hashing, aka "Windows Code Integrity Module Denial of Service Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.

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 confidence

A denial of service vulnerability in the Windows Code Integrity Module's hashing implementation. An attacker with local access could exploit how the module processes hash validation, causing the system to become unresponsive or crash. This affects the kernel-level code integrity checking that validates driver and system file signatures.

MitigationApply the relevant Microsoft security update for CVE-2018-1040 through standard patch management processes. In enterprise environments, test patches in a controlled manner before broad deployment to ensure compatibility with existing driver configurations.

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= 1703= 1709= 1807
Windows 7Operating system
Affected:all versions
Windows 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= 1709= 1803

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
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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 checks

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

  1. Identify Windows version
    Run 'systeminfo' or 'winver' and note the Windows version and build number. Compare against the listed affected versions: Windows 10 (1511, 1607, 1703, 1709, 1807), Windows 7 (all), Windows 8.1 (all), Windows Server 2008 (all and R2), Windows Server 2012 (all and R2), Windows Server 2016 (all, 1709, 1803).
    Affected if The installed version matches one of the affected versions listed in the CVE.
  2. Confirm Code Integrity is enabled
    Open an elevated command prompt and run 'verifier /query' or check the Code Integrity status via 'sigverif' command. Alternatively, verify Driver Signature Enforcement is active by checking that 64-bit Windows is running with mandatory driver signing in place.
    Affected if Code Integrity / Driver Signature Enforcement is enabled (this is the default on most supported Windows versions and required for the vulnerability to be exploitable).
  3. Check for the presence of the vulnerable Code Integrity module
    Examine the version of the Code Integrity module (ci.dll) in the System32 folder. Run 'dir C:\Windows\System32\ci.dll' to view file version details, or use 'wmic datafile where "name='C:\\Windows\\System32\\ci.dll'" get Version,FileSize,LastModified'.
    Affected if The ci.dll version corresponds to an unpatched build from an affected Windows version; the file timestamp predates the security update release date.

You are affected if your system runs an unpatched Windows version from the affected list AND Code Integrity/Driver Signature Enforcement is enabled, which is the default configuration.

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 relevant Microsoft security update for CVE-2018-1040 through standard patch management processes. In enterprise environments, test patches in a controlled manner before broad deployment to ensure compatibility with existing driver configurations.

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

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1040 — 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-2018-1040 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