Security readout for executives and security teams
Plain-English summary
CVE-2022-21845 is a Windows Kernel information disclosure issue. A local attacker with low privileges could potentially expose sensitive information, but the published CVSS data shows high attack complexity and no direct integrity or availability impact.
Executive priority
Handle through normal Windows patch governance, with added attention to legacy or shared systems. This is not a crisis signal from the provided evidence, but it can increase risk when chained with other local attacks.
Technical view
The CVSS vector is local, high complexity, low privileges required, no user interaction, unchanged scope, and high confidentiality impact only. Microsoft lists multiple Windows client and server versions as affected and provides the vendor advisory reference.
Likely exposure
Exposure is most likely on affected Windows endpoints and servers that have not received the applicable Microsoft security updates, especially legacy Windows 7, 8.1, Server 2008, Server 2016, Server 2019, Server 2022, Windows 10, and Windows 11 builds listed in the source bundle.
Exploitation context
The provided sources do not support active exploitation. The CVSS exploit maturity is Unproven, and the bundle marks this CVE as not in KEV. Exploitation requires local access with low privileges and high complexity.
Researcher notes
Public source detail is sparse: no CWE, component internals, proof of concept, or exploit technique are provided in the bundle. Treat this as a confidentiality-only local kernel issue and avoid assuming exploitation paths beyond the CVSS and Microsoft advisory data.
Mitigation direction
- Review the Microsoft MSRC advisory for applicable updates.
- Apply Microsoft security updates for affected Windows versions.
- Prioritize shared systems, servers, and endpoints with local user access.
- Retire, upgrade, or isolate unsupported legacy Windows systems.
- Track vendor guidance for any advisory revisions.
Validation and detection
- Inventory Windows versions against the affected product list.
- Check patch compliance against the MSRC advisory.
- Confirm vulnerability scanner findings reference CVE-2022-21845.
- Validate legacy Windows systems are upgraded, isolated, or risk-accepted.
- Recheck exposure after monthly patch cycles.
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.
CVE-2022-21845 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.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/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.
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:N/A:N/E:U/RL:O/RC:C13.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.7MediumVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- Windows Kernel Information Disclosure VulnerabilityCVE reference · vendor-advisory
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.