Security readout for executives and security teams
Plain-English summary
This Windows kernel flaw could let an attacker who already has low-level local access gain greater control over an affected computer. It is serious because successful exploitation could compromise confidentiality, integrity, and availability, but it is not a remote, unauthenticated attack and requires high attack complexity.
Executive priority
Prioritize remediation within the normal high-severity patch window, accelerating internet-facing servers, shared systems, and endpoints at elevated compromise risk. This is not documented as actively exploited, but it can amplify an existing foothold into a substantially more damaging compromise.
Technical view
CVE-2024-30099 is a Windows kernel elevation-of-privilege vulnerability categorized as CWE-367, a time-of-check/time-of-use race condition. Its CVSS 3.1 score is 7.0: local access and low privileges are required, attack complexity is high, no user interaction is needed, and successful exploitation can have high confidentiality, integrity, and availability impact.
Likely exposure
Potential exposure includes the listed Windows 10 and Windows 11 releases, plus Windows Server 2016, 2019, 2022, and Server Core variants. Risk is greatest where low-privileged users or compromised applications can execute locally. The supplied evidence does not provide configuration-specific exposure conditions.
Exploitation context
The supplied bundle marks this CVE as not present in CISA KEV and provides no evidence of active exploitation. The CVSS vector reports proof-of-concept exploit maturity, but local access, existing low privileges, and high attack complexity constrain exploitation. Treat it primarily as a post-compromise privilege-escalation risk.
Researcher notes
The evidence identifies a kernel race condition but does not name the precise kernel component, reachable code path, exploitation mechanics, or applicable KB numbers. The affected list also contains duplicate Windows 10 1809 and Windows 11 23H2 entries. Consult the Microsoft advisory for authoritative update applicability; do not infer exposure solely from product naming.
Mitigation direction
- Review the MSRC advisory and deploy its applicable security update to affected Windows systems.
- Prioritize systems where low-privileged users or compromised applications can execute locally.
- Reduce unnecessary low-privileged local access until security updates are verified.
Validation and detection
- Inventory systems running the Windows releases identified in the affected-product list.
- Compare installed update records with the remediation specified in Microsoft’s CVE advisory.
- Rescan updated systems and investigate any devices still reporting CVE-2024-30099 exposure.
- Confirm unsupported or unverified systems are tracked for compensating controls or replacement.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-367: 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 lookupPrivilege 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 lookupCVE-2024-30099 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C15.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Windows Kernel Elevation of Privilege VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.