CriticalCVE-2024-30088

    Windows Kernel Elevation of Privilege Vulnerability (CVE-2024-30088)

    Published Last modified In CISA KEV since Sources: pwn.watch, CVE.org

    Share

    What is affected, what to do

    Windows Kernel Elevation of Privilege Vulnerability

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update Microsoft Windows 10 Version 1507 to version 10.0.10240.20680, Microsoft Windows 10 Version 1607 to version 10.0.14393.7070, Microsoft Windows 10 Version 1809 to version 10.0.17763.5936. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Windows 10 Version 1507 lt 10.0.10240.0..10.0.10240.20680
    • Microsoft Windows 10 Version 1607 lt 10.0.14393.0..10.0.14393.7070
    • Microsoft Windows 10 Version 1809 lt 10.0.17763.0..10.0.17763.5936
    • Microsoft Windows 10 Version 21H2 lt 10.0.19044.0..10.0.19044.4529
    • Microsoft Windows 10 Version 22H2 lt 10.0.19045.0..10.0.19045.4529
    • Microsoft Windows 11 version 21H2 lt 10.0.22000.0..10.0.22000.3019
    • Microsoft Windows 11 version 22H2 lt 10.0.22621.0..10.0.22621.3737
    • Microsoft Windows 11 version 23H2 lt 10.0.22631.0..10.0.22631.3737
    • Microsoft Windows Server 2016 lt 10.0.14393.0..10.0.14393.7070
    • Microsoft Windows Server 2016 (Server Core installation) lt 10.0.14393.0..10.0.14393.7070
    • Microsoft Windows Server 2019 lt 10.0.17763.0..10.0.17763.5936
    • Microsoft Windows Server 2019 (Server Core installation) lt 10.0.17763.0..10.0.17763.5936
    • Microsoft Windows Server 2022 lt 10.0.20348.0..10.0.20348.2527
    • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) lt 10.0.25398.0..10.0.25398.950
    Fixed in
    • Microsoft Windows 10 Version 1507 10.0.10240.20680
    • Microsoft Windows 10 Version 1607 10.0.14393.7070
    • Microsoft Windows 10 Version 1809 10.0.17763.5936
    • Microsoft Windows 10 Version 21H2 10.0.19044.4529
    • Microsoft Windows 10 Version 22H2 10.0.19045.4529
    • Microsoft Windows 11 version 21H2 10.0.22000.3019
    • Microsoft Windows 11 version 22H2 10.0.22621.3737
    • Microsoft Windows 11 version 23H2 10.0.22631.3737
    • Microsoft Windows Server 2016 10.0.14393.7070
    • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.7070
    • Microsoft Windows Server 2019 10.0.17763.5936
    • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.5936
    • Microsoft Windows Server 2022 10.0.20348.2527
    • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.950

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.0

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: pwn.watch, CVE.org

    68.2 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.33

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    244.30 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    68.2 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.33
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 10 June 2024
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-367

    Response and mitigation

    Why act now?

    Prioritisation rationale

    Exploitation requires local access and wins a race with high attack complexity. However, a public, reliable exploit has turned this bug into a commodity post-access privilege-escalation step, and exploitation likelihood is very high. CISA flags known use in ransomware campaigns. Attackers typically chain it after phishing, webshell deployment or abuse of a compromised account to obtain SYSTEM, kill security tooling and harvest credentials. Organisations with many multi-user hosts (RDS, VDI) or internet-facing services on Windows servers should treat remediation as a high-priority patch item to close within days. It should be escalated to critical wherever initial access to an unpatched host is confirmed.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the June 2024 Patch Tuesday security update, or any later cumulative update, to all Windows clients and servers. Per the context, the fixed build thresholds are: Windows 10 1507 10.0.10240.20680, 1607/Server 2016 10.0.14393.7070, 1809/Server 2019 10.0.17763.5936, 21H2 10.0.19044.4529, 22H2 10.0.19045.4529, Windows 11 21H2 10.0.22000.3019 and 22H2 10.0.22621.3737. Look up the exact KB number per edition in the MSRC advisory for CVE-2024-30088.
      • Pull build inventory from Intune, SCCM/MECM, WSUS or Defender Vulnerability Management. Treat anything below the listed builds as vulnerable. Tackle these first: RDS/terminal servers, VDI, jump hosts, domain controllers and other multi-user systems.
      • Isolate hosts via EDR wherever there are signs of initial access, such as a phishing payload, a compromised VPN account or a webshell. This bug is the second stage of an attack chain, not the entry point.
      • On hosts with indicators of compromise, treat local and cached credentials as exposed. Rotate service accounts and local admin passwords (via LAPS), and review cached domain logons.
      • Record any systems that cannot be patched quickly, such as legacy or out-of-support builds, as tracked exceptions with a deadline and compensating controls.
    2. Runbook step 2

      Mitigation layers

      • No vendor workaround: No configuration change closes this kernel race condition. Compensating controls only reduce the likelihood of exploitation or limit the blast radius.
      • Application control: Enforce WDAC or AppLocker and block unsigned binaries from user-writable paths (%TEMP%, %APPDATA%, %LOCALAPPDATA%, C:\Users\Public, Downloads). Public exploits typically arrive as a standalone EXE or are loaded reflectively.
      • Endpoint hardening: Enable LSA protection (RunAsPPL) and Credential Guard so that a SYSTEM shell does not translate directly into an LSASS dump. Enforce EDR tamper protection, because attackers with SYSTEM rights routinely try to disable security tooling. Enable ASR rules, in particular "Block credential stealing from LSASS" and the prevalence/age-based executable rule.
      • IAM / least privilege: Apply admin tiering. Use GPO ("Deny log on locally" and "Deny log on through Remote Desktop Services") to stop standard users from logging on interactively to critical servers.
      • Network segmentation: Limit lateral movement after a successful privilege escalation. Block SMB (445/tcp), WinRM (5985/5986/tcp) and RDP (3389/tcp) between client segments, and force admin access through dedicated jump hosts.
    3. Runbook step 3

      Detection rules

      • Defender/EDR (KQL): Detect a SYSTEM process spawned by a lower-integrity parent: DeviceProcessEvents | where ProcessIntegrityLevel == "System" and InitiatingProcessIntegrityLevel in ("Medium","Low") and InitiatingProcessAccountName !endswith "$". Typical children are cmd.exe, powershell.exe, whoami.exe and net.exe.
      • Sysmon EID 1 / Security 4688: Look for a process running as NT AUTHORITY\SYSTEM whose parent runs as a regular user and is not services.exe, svchost.exe or wininit.exe. Sigma shape: selection: User|contains: 'SYSTEM', filtered on ParentUser not SYSTEM and ParentImage not in the service-host allowlist.
      • Sysmon EID 11 + EID 1: An unsigned EXE is written to %TEMP%, %APPDATA% or C:\Users\Public, executes shortly afterwards, and then spawns a SYSTEM child within seconds. Correlate on ProcessGuid / ParentProcessGuid.
      • Post-exploitation: Watch for Sysmon EID 10 events where a non-allowlisted process accesses lsass.exe (GrantedAccess 0x1010 or 0x1FFFFF). Also watch for new service installs (System 7045, Security 4697) and Defender event 5001 ("Real-time protection disabled") shortly after a suspicious process launch.
      • Behavioural anomaly: Where your EDR exposes thread telemetry, hunt for user-context processes with abnormal thread-creation bursts (the race loop) followed immediately by a SYSTEM-level child process.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Windows Kernel Elevation of Privilege Vulnerability

    Source: pwn.watch, CISA KEV Catalog, cvelistv5, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftWindows 10 Version 1507
    • 10.0.10240.0 – < 10.0.10240.20680
    • 10.0.10240.20680
    MicrosoftWindows 10 Version 1607
    • 10.0.14393.0 – < 10.0.14393.7070
    • 10.0.14393.7070
    MicrosoftWindows 10 Version 1809
    • 10.0.17763.0 – < 10.0.17763.5936
    • 10.0.17763.5936
    MicrosoftWindows 10 Version 21H2
    • 10.0.19044.0 – < 10.0.19044.4529
    • 10.0.19044.4529
    MicrosoftWindows 10 Version 22H2
    • 10.0.19045.0 – < 10.0.19045.4529
    • 10.0.19045.4529
    MicrosoftWindows 11 version 21H2
    • 10.0.22000.0 – < 10.0.22000.3019
    • 10.0.22000.3019
    MicrosoftWindows 11 version 22H2
    • 10.0.22621.0 – < 10.0.22621.3737
    • 10.0.22621.3737
    MicrosoftWindows 11 version 23H2
    • 10.0.22631.0 – < 10.0.22631.3737
    • 10.0.22631.3737
    MicrosoftWindows Server 2016
    • 10.0.14393.0 – < 10.0.14393.7070
    • 10.0.14393.7070
    MicrosoftWindows Server 2016 (Server Core installation)
    • 10.0.14393.0 – < 10.0.14393.7070
    • 10.0.14393.7070
    MicrosoftWindows Server 2019
    • 10.0.17763.0 – < 10.0.17763.5936
    • 10.0.17763.5936
    MicrosoftWindows Server 2019 (Server Core installation)
    • 10.0.17763.0 – < 10.0.17763.5936
    • 10.0.17763.5936
    MicrosoftWindows Server 2022
    • 10.0.20348.0 – < 10.0.20348.2527
    • 10.0.20348.2527
    MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)
    • 10.0.25398.0 – < 10.0.25398.950
    • 10.0.25398.950

    Vendors and products

    Affected operating systems

    Affected operating systems
    Windowsmicrosoftwindows_10_1507—
    Windowsmicrosoftwindows_10_1607—
    Windowsmicrosoftwindows_10_1809—
    Windowsmicrosoftwindows_10_21h2—
    Windowsmicrosoftwindows_10_22h2—
    Windowsmicrosoftwindows_11_21h2—
    Windowsmicrosoftwindows_11_22h2—
    Windowsmicrosoftwindows_11_23h2—
    Windowsmicrosoftwindows_server_2016—
    Windowsmicrosoftwindows_server_2019—
    Windowsmicrosoftwindows_server_2022—
    Windowsmicrosoftwindows_server_2022_23h2—

    Weakness classes (CWE)

    • CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition

      Base

      The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

      Entry at MITRE CWE-367

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedMicrosoft

      1 individual change: Affected versions (publisher)

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)changed
      Windows 10 Version 1809, Windows 10 Version 1809, Windows Server 2019 (+13)
      Windows 10 Version 1507, Windows 10 Version 1607, Windows 10 Version 1809 (+13)

      Source identifier: secure@microsoft.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-30088
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-30088"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-30088.svg?lang=en" alt="CVE-2024-30088 – NEOSEC Intel" height="20"></a>