Security readout for executives and security teams
Plain-English summary
CVE-2022-35767 is a high-severity Microsoft Windows flaw in Secure Socket Tunneling Protocol. A remote, unauthenticated attacker could potentially run code on affected systems, but the CVSS vector marks exploitation as high complexity. Treat exposed Windows systems using SSTP as the main business concern.
Executive priority
Prioritize remediation for internet-facing or partner-facing Windows systems that use SSTP. This is not evidenced as actively exploited in the provided sources, but remote unauthenticated code execution on Windows infrastructure justifies prompt patch governance.
Technical view
The issue is a Windows SSTP remote code execution vulnerability mapped to CWE-94, with CVSS 3.1 score 8.1. The vector is network, no privileges, no user interaction, unchanged scope, and high impact to confidentiality, integrity, and availability. Microsoft lists an official remediation state.
Likely exposure
Exposure is most likely on affected Windows client or server versions where SSTP is installed, enabled, or reachable over the network. The bundle lists Windows 7, 8.1, 10, 11, Server 2008, 2016, 2019, 2022, and Server Core variants.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. CVSS marks exploit maturity as unproven. Risk remains meaningful because attack requires no authentication or user interaction, although attack complexity is rated high.
Researcher notes
The bundle does not include root-cause detail, exploit primitives, proof-of-concept status, or precise service prerequisites beyond SSTP. Validation should stay focused on Microsoft affected-product matching, exposure discovery, and update verification rather than assumed exploit behavior.
Mitigation direction
- Apply the relevant Microsoft security update for each affected Windows version.
- Review the MSRC advisory for exact product-specific remediation guidance.
- Prioritize systems exposing SSTP to untrusted networks.
- Retire or isolate affected systems that cannot receive Microsoft updates.
- Track remediation through vulnerability management until scanners show closure.
Validation and detection
- Inventory Windows hosts matching the affected versions listed by Microsoft.
- Identify systems where SSTP is installed, enabled, or network-reachable.
- Confirm patch status against the MSRC CVE-2022-35767 advisory.
- Validate vulnerability scanner results after updates are applied.
- Document any unpatched exceptions with compensating controls and owners.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-2022-35767 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
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/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:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/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 Secure Socket Tunneling Protocol (SSTP) Remote Code Execution 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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.