Security readout for executives and security teams
Plain-English summary
This Windows kernel flaw can let a locally authenticated attacker bypass a security protection and make unauthorized integrity changes. It does not provide remote entry by itself, but it can strengthen an attacker’s position after they gain limited access to an affected Windows device.
Executive priority
Handle through the normal security-update cycle with elevated attention for multi-user systems and critical servers. Emergency internet-edge remediation is not indicated by the supplied evidence, but deferral increases post-compromise risk because exploitation needs only low local privileges.
Technical view
CVE-2024-21362 is a Windows kernel security-feature bypass associated with CWE-367, a time-of-check/time-of-use race condition. The CVSS 3.1 vector indicates local access, low complexity, low privileges, no user interaction, and high integrity impact, without identified confidentiality or availability impact.
Likely exposure
Exposure spans listed Windows 10, Windows 11, Windows Server 2016, 2019, and 2022 releases, including several Server Core installations. Systems matching the specified editions and builds should be treated as potentially exposed until Microsoft’s update applicability and installation status are confirmed.
Exploitation context
The supplied evidence does not establish active exploitation, and the CVE is not identified as a CISA KEV entry. Exploitation requires local access and low privileges, making this principally a post-compromise or insider-risk concern rather than a direct remote-entry vulnerability.
Researcher notes
The available data identifies CWE-367 but does not describe the vulnerable kernel operation, affected security boundary, attack primitive, indicators, or specific fixed builds. Researchers should rely on Microsoft’s advisory and update metadata for precise applicability; stronger exploitability claims are unsupported by this bundle.
Mitigation direction
- Review Microsoft’s advisory and deploy the applicable security update for each affected Windows edition.
- Prioritize shared workstations, servers, and systems where untrusted users can obtain local accounts.
- Restrict unnecessary local access while updates are being validated and deployed.
- Follow current Microsoft guidance if an applicable update cannot be installed promptly.
Validation and detection
- Inventory Windows editions, versions, builds, and Server Core installations against the supplied affected list.
- Use Microsoft’s advisory to identify the applicable security update for each system.
- Verify successful update installation through endpoint or patch-management records.
- Investigate affected systems showing unexpected privileged integrity changes or suspicious local account 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 lookupCVE-2024-21362 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
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/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:L/PR:L/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C1.83.6microsoftVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/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 Security Feature Bypass 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.