Security readout for executives and security teams
Plain-English summary
This flaw lets a user who already has limited access to a Windows machine potentially gain higher privileges through the Windows CNG Key Isolation Service. It is not a remote break-in by itself, but CISA lists it in KEV, meaning real-world exploitation is confirmed. Treat unpatched Windows endpoints and servers as priority remediation targets.
Executive priority
High priority. This is a confirmed exploited Windows privilege-escalation flaw with official fixes available. It should be handled as part of urgent patch governance, especially on systems where compromise would enable domain movement, credential access, or administrative control.
Technical view
CVE-2023-28229 is a Windows CNG Key Isolation Service elevation-of-privilege issue, rated CVSS 7.0 with local attack vector, high complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact. Microsoft marks an official fix as available. The bundle maps it to CWE-591.
Likely exposure
Exposure is likely on unpatched supported or legacy Windows systems listed by Microsoft, including Windows 10, Windows 11, and Windows Server 2008 through 2022 variants. Local access is required, so risk is highest on shared systems, VDI, workstations, and servers where an attacker may already have a foothold.
Exploitation context
CISA KEV inclusion supports active exploitation in the wild. The provided CVSS data shows exploitation requires local access and low privileges, with high attack complexity. The sources do not provide public exploit mechanics, campaign details, or attacker tooling, so those should not be assumed.
Researcher notes
The supplied evidence confirms affected products, CVSS characteristics, vendor fix availability, and KEV status. It does not include root-cause detail, exploit primitives, or reliable indicators of compromise. Validation should focus on patch state and exposure mapping rather than attempting exploit reproduction.
Mitigation direction
- Apply Microsoft security updates for CVE-2023-28229 on all affected Windows systems.
- Prioritize internet-adjacent, shared, admin, and high-value Windows assets first.
- Check Microsoft guidance for exact KBs by Windows version and servicing channel.
- Reduce local user access where it is no longer needed.
- Retire or isolate unsupported Windows versions that cannot receive fixes.
Validation and detection
- Inventory Windows endpoints and servers against Microsoft’s affected product list.
- Confirm the relevant Microsoft update is installed for each affected build.
- Review vulnerability scanner results for CVE-2023-28229 after patch deployment.
- Check CISA KEV tracking for required remediation timelines in regulated environments.
- Monitor endpoints for suspicious local privilege escalation activity.
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-591: 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-2023-28229 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
- Yes
- 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.
CISA KEV status
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.9Primary CVE scoreVulnerability 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
Source materials
- CVE List V5 sourceCVE List V5
- Windows CNG Key Isolation Service Elevation of Privilege VulnerabilityCVE reference · vendor-advisory
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-28229CVE reference · government-resource
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.
Sensitive Data Storage in Improperly Locked Memory
Sensitive Data Storage in Improperly Locked Memory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.