Security readout for executives and security teams
Plain-English summary
A flaw in Microsoft’s PEAP implementation could allow a remote, unauthenticated attacker to execute code on affected Windows systems without user interaction. Successful exploitation could compromise confidentiality, integrity, and availability. Exposure depends on whether affected Windows versions use PEAP and whether Microsoft’s corresponding security update is installed.
Executive priority
Treat as an urgent patch-management issue because the documented impact is remote code execution with critical severity and no required authentication or user action. Rapidly identify PEAP-dependent assets, apply Microsoft’s update, and verify deployment. There is no supplied evidence of active exploitation, so urgency is driven by technical severity and exposure potential.
Technical view
CVE-2023-21690 is a heap-based buffer overflow (CWE-122) in Microsoft Protected Extensible Authentication Protocol. Its CVSS 3.1 score is 9.8, with network reachability, low attack complexity, no required privileges, and no user interaction. Microsoft lists numerous Windows client and server releases as affected and provides a security update advisory.
Likely exposure
Potentially exposed assets include the listed Windows 10, Windows 11, and Windows Server releases where PEAP is enabled or used. The supplied evidence does not establish that every installation is reachable or exploitable. Prioritize systems participating in PEAP authentication and systems lacking the Microsoft security update.
Exploitation context
The supplied bundle does not identify this CVE as present in CISA’s Known Exploited Vulnerabilities catalog and provides no evidence of active exploitation. The CVSS vector nevertheless indicates potentially remote, unauthenticated exploitation without user interaction. Treat exploitation status as unconfirmed, not impossible.
Researcher notes
The strongest supplied signals are Microsoft’s RCE classification, CWE-122, and the 9.8 CVSS vector. The bundle does not provide vulnerable code paths, exploit prerequisites beyond the scoring vector, public proof-of-concept evidence, or observed attacks. Validate product applicability and update status through Microsoft’s advisory; avoid inferring universal reachability from the network vector alone.
Mitigation direction
- Apply the applicable Microsoft security update referenced in the vendor advisory.
- Prioritize affected systems that enable or participate in PEAP authentication.
- Review Microsoft guidance for any prerequisites, deployment considerations, or supported mitigations.
- Reduce unnecessary PEAP exposure until updates are verified across affected assets.
Validation and detection
- Inventory Windows editions, versions, and build numbers against Microsoft’s affected-product list.
- Identify endpoints and servers configured to use PEAP authentication.
- Verify the applicable Microsoft security update is installed successfully.
- Confirm vulnerability scanners recognize patched systems without relying solely on operating-system version.
- Monitor authentication infrastructure and affected hosts for unusual PEAP-related failures or security events.
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-122: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-21690 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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.
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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C3.95.9microsoftVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/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
- Microsoft Protected Extensible Authentication Protocol (PEAP) Remote Code Execution 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.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.