cve.bz

CVE-2018-8611 Microsoft Windows Kernel Privilege Escalation Vulnerability

7.8 highKEVEPSS 4.2%Fix available

High (7.8) in Microsoft Windows. In CISA KEV since 2022-05-24. EPSS 4.2% estimated probability of exploitation activity in the next 30 days.

On this page
An elevation of privilege vulnerability exists when the Windows kernel fails to properly handle objects in memory, aka "Windows Kernel Elevation of Privilege Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2019, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
4.2% (unchanged from 4.2% a week ago; 4.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 91st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-05-24, due 2022-06-14
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-8611 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-8611?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-8611?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-8611 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
microsoft:windows_server_2008r2
microsoft:windows_server_2012r2

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • ahm3dgg/cve-2018-8611 Harbor Check: matches CVE 1 star, C++, created
    CVE-2018-8611 PrivEsc Exploit

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON