Security readout for executives and security teams
Plain-English summary
This Windows kernel flaw may let an attacker with physical access expose sensitive memory. It does not alter data or disrupt service, but disclosed information could support further attacks. The supplied CVSS score is 4.6, making this a moderate concern rather than an emergency.
Executive priority
Handle through the normal security-patching cycle, accelerating remediation for physically accessible or sensitive systems. The confidentiality impact is potentially serious, but required physical access and absent evidence of active exploitation reduce immediate enterprise-wide urgency.
Technical view
CVE-2024-21340 is a Windows kernel information-disclosure vulnerability categorized as CWE-126, an out-of-bounds read. The supplied vector requires physical access but no privileges or user interaction. Successful exploitation can cause high confidentiality impact, with no stated integrity or availability impact.
Likely exposure
Exposure is limited to affected Windows builds listed in the bundle, spanning specified Windows 10, Windows 11, and Windows Server releases through Server 2016. Prioritize physically accessible endpoints, shared devices, kiosks, and servers. The bundle does not establish exposure for products or versions outside its list.
Exploitation context
The supplied record does not identify this CVE as CISA KEV-listed and provides no evidence of active exploitation. Its CVSS exploit-maturity value is unproven. Physical access is required, substantially limiting remote attack scenarios, although local information disclosure could contribute to a broader attack chain.
Researcher notes
The available evidence identifies CWE-126 and a physical attack vector, but provides no vulnerable component, trigger details, or disclosed-memory scope. Treat deeper root-cause or exploitability claims as unverified. Consult Microsoft’s advisory for update applicability and any additional technical details.
Mitigation direction
- Apply the Microsoft security update identified in the vendor advisory.
- Inventory affected Windows editions and builds across endpoints and servers.
- Restrict physical access to affected systems until updates are confirmed.
- Check Microsoft guidance for release-specific prerequisites or servicing requirements.
Validation and detection
- Compare installed Windows editions and builds against the supplied affected-product list.
- Confirm the applicable Microsoft security update is installed successfully.
- Review update-management records for failures, exclusions, and pending restarts.
- Reassess physically exposed or shared systems for compensating access controls.
Public sources used
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-126: 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-21340 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
- 4.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C0.93.6microsoftVulnerability scoring details
Base CVSS 3.1 score
4.6MediumVector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Information Disclosure 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.
Buffer Over-read
Buffer Over-read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.