LiveActive security incident?Get immediate response
CVE Record

CVE-2024-30086: Windows Win32 Kernel Subsystem Elevation of Privilege Vulnerability

Windows Win32 Kernel Subsystem Elevation of Privilege Vulnerability

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local attacker with an existing low-privilege account could exploit a Windows kernel memory flaw to gain elevated privileges. Successful exploitation could provide broad control over the affected device, including access to sensitive information and the ability to alter or disrupt systems.

Executive priority

Treat this as a high-priority patching issue, particularly on shared endpoints, exposed servers, and systems where initial compromise would threaten sensitive operations. It is not described as remotely exploitable, but it could turn limited access into extensive device control.

Technical view

CVE-2024-30086 is a Win32 Kernel Subsystem elevation-of-privilege vulnerability classified as CWE-416, use-after-free. It has CVSS 3.1 score 7.8 and requires local access with low privileges, low complexity, and no user interaction. Successful exploitation can cause high confidentiality, integrity, and availability impact.

Likely exposure

Exposure includes the listed Windows 10 and Windows 11 releases and Windows Server 2012 through 2022 variants, including specified Server Core installations. Organizations should match deployed editions and builds against Microsoft’s advisory; the bundle does not provide fixed build or KB details.

Exploitation context

The supplied record does not indicate CISA KEV inclusion or provide evidence of active exploitation. Exploitation requires an attacker to already have local low-privilege access, making this especially relevant after credential compromise, malware execution, or another initial-access event.

Researcher notes

The source bundle identifies a kernel use-after-free but does not describe the vulnerable function, triggering conditions, affected component internals, proof-of-concept availability, or fixed builds. Consult Microsoft’s advisory for authoritative remediation mappings. No conclusion about real-world exploitation should be drawn solely from absence from KEV.

Mitigation direction

  • Review Microsoft’s CVE advisory for applicable security updates and installation requirements.
  • Apply the relevant Microsoft security updates to affected supported Windows systems.
  • Prioritize endpoints and servers accessible to untrusted or lower-privileged users.
  • Restrict unnecessary local accounts and administrative access while remediation is underway.
  • Use endpoint monitoring to detect suspicious privilege changes and kernel-related failures.

Validation and detection

  • Inventory Windows editions, versions, build numbers, and Server Core installations.
  • Compare each inventoried system with Microsoft’s affected and fixed-version guidance.
  • Confirm applicable security updates installed successfully and survived required restarts.
  • Verify vulnerability scanners recognize systems as remediated after patching.
  • Review endpoint telemetry for unexplained privilege escalation or abnormal kernel crashes.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-30086 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-30086Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 150710.0.10240.0Listed
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 180910.0.0Listed
MicrosoftWindows 10 Version 21H210.0.19044.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 21H210.0.22000.0Listed
MicrosoftWindows 11 version 22H210.0.22621.0Listed
MicrosoftWindows 11 version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.