Security readout for executives and security teams
Plain-English summary
This Microsoft Windows flaw can let a remote, unauthenticated attacker cause a denial of service in affected Windows systems. The known impact is availability loss, not data theft or code execution. Because many client and server Windows versions are listed, organizations should treat patch verification as a broad Windows fleet hygiene priority.
Executive priority
Prioritize this as a high availability risk, not a breach-confirmed emergency. The vulnerability is remotely reachable and requires no authentication, but current provided evidence does not show active exploitation or confidentiality impact. Patch affected Windows systems through normal expedited maintenance, starting with critical servers.
Technical view
CVE-2023-35330 is a Windows Extended Negotiation denial-of-service vulnerability with CVSS 3.1 score 7.5. The vector is network-accessible, low complexity, no privileges, and no user interaction, with high availability impact only. The listed weakness is CWE-126, out-of-bounds read. Microsoft published vendor guidance for affected Windows builds.
Likely exposure
Exposure is likely wherever listed Windows 10, Windows 11, and Windows Server versions remain unpatched, especially reachable server systems. The source bundle does not specify affected ports, protocol preconditions, or vulnerable configuration details, so exposure should be confirmed through Microsoft guidance and asset inventory.
Exploitation context
The sources do not support active exploitation. The CVSS temporal metric marks exploit code maturity as unproven, and the CVE is not listed as CISA KEV in the provided bundle. The practical risk is remote service disruption if vulnerable systems are reachable and not updated.
Researcher notes
The bundle lacks protocol-level details, crash behavior, affected components beyond Extended Negotiation, and exact patch identifiers. Avoid assuming exploitability beyond remote denial of service. Validation should rely on Microsoft advisory applicability, installed update evidence, and asset exposure rather than exploit reproduction.
Mitigation direction
- Review the Microsoft MSRC advisory for applicable updates by Windows version.
- Deploy the official Microsoft security update across affected Windows client and server builds.
- Prioritize internet-facing, remote-accessible, and business-critical Windows servers.
- Monitor availability after patching because the documented impact is denial of service.
- Check vendor guidance if a listed legacy platform has special servicing requirements.
Validation and detection
- Inventory Windows versions against the affected product list in the source bundle.
- Confirm each affected build has the relevant Microsoft security update installed.
- Validate that high-priority exposed Windows servers are patched first.
- Review vulnerability scanner findings against MSRC advisory status and installed patch evidence.
- Track exceptions with business owner, exposure notes, and remediation target date.
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-2023-35330 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.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:N/I:N/A:H/E:U/RL:O/RC:C3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- Windows Extended Negotiation Denial of Service 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.
Buffer Over-read
Buffer Over-read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.