Security readout for executives and security teams
Plain-English summary
This Windows Kernel flaw could let a user or malicious code already running on an affected system gain elevated privileges. It is not remotely exploitable by itself, but successful abuse could compromise confidentiality, integrity, and availability. The supplied record rates it high severity.
Executive priority
Treat as a high-priority patching item, especially on systems where untrusted users or compromised applications could run locally. It does not warrant the urgency of a confirmed remotely exploited critical flaw, but delayed remediation could help an attacker turn limited access into broad system control.
Technical view
CVE-2024-21371 is a Windows Kernel elevation-of-privilege vulnerability categorized as CWE-367, a time-of-check/time-of-use race condition. CVSS 3.1 is 7.0: local access, low privileges, high attack complexity, and no user interaction. Successful exploitation can cause high confidentiality, integrity, and availability impact.
Likely exposure
Exposure includes the listed Windows 10, Windows 11, and Windows Server 2012 through 2022 releases, including specified Server Core installations. An attacker first needs low-privileged local access or code execution. Inventory and update status are necessary to determine actual organizational exposure.
Exploitation context
The supplied sources do not establish active exploitation, and the record is not identified as CISA KEV. Exploitation requires local access, low privileges, and high complexity, without user interaction. It is therefore more relevant for privilege escalation after an attacker gains an initial foothold than for direct remote compromise.
Researcher notes
The source bundle identifies CWE-367 but provides no affected kernel component, race window, proof of concept, or confirmed exploitation evidence. CVSS reports high complexity and local attack scope. Validate affected builds and remediation through Microsoft’s advisory; do not infer exploitability for unlisted versions.
Mitigation direction
- Apply the applicable Microsoft security update for each affected Windows release.
- Prioritize internet-facing, shared, administrator-used, and high-value Windows systems.
- Restrict unnecessary local access and application execution until systems are updated.
- Consult Microsoft guidance for release-specific prerequisites and servicing instructions.
Validation and detection
- Inventory systems running the Windows releases listed in the CVE record.
- Verify applicable Microsoft security updates are installed successfully on each system.
- Confirm systems restarted if required and update installation reports show no failures.
- Review endpoint telemetry for unexpected privilege elevation or suspicious local activity.
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-21371 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:U/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:U/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:U/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.