CVE-2018-8205
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 · uneditedA denial of service vulnerability exists when Windows improperly handles objects in memory, aka "Windows Denial of Service Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, 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 · high confidenceA denial of service vulnerability exists in Windows where improper handling of objects in memory allows an attacker to crash the affected system. The vulnerability requires no authentication and can be exploited remotely or locally.
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 dataall versions= 1607= 1703= 1709= 1803all versionsall versionsall versions= r2all versions= r2all versions= 1709= 1803CVSS 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.0/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 Windows version and build numberRun 'winver' from command prompt or check 'systeminfo' output. Look at the OS Name and Version fields. Alternatively, read the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and note the values of 'CurrentBuild', 'CurrentBuildNumber', and 'ReleaseId'.Affected if The version matches any of these: Windows 10 (any version including 1607, 1703, 1709, 1803); Windows 7 (any version); Windows 8.1 (any version); Windows RT 8.1; Windows Server 2008 R2; Windows Server 2012 (any version including R2); Windows Server 2016 (any version including 1709, 1803).
-
Check if security update KB4338823 is installedRun 'wmic qfe list' or use PowerShell with 'Get-HotFix | Where-Object {$_.HotFixID -eq "KB4338823"}'. Alternatively, open Control Panel > Programs > Programs and Features > View installed updates and search for KB4338823.Affected if The output does not show KB4338823 or a later cumulative security update for this month (June 2018 or newer).
-
Verify Windows Update is up to dateOpen Settings > Update & Security > Windows Update and click 'Check for updates'. Review the update history or run 'Get-WindowsUpdateLog' to parse the update log.Affected if No security updates from June 2018 or later are installed, or the system has not been patched through Windows Update.
You are affected if your Windows version matches the affected list AND no June 2018 or later security update (KB4338823 or subsequent) is installed on the system.
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 dataApply the Microsoft security update (KB4338823 or subsequent patches) to all affected Windows systems. This is a standard patch deployment task with no configuration changes required.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8205 — 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-8205 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