LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34714: Windows Secure Socket Tunneling Protocol (SSTP) Remote Code Execution Vulnerability

Windows Secure Socket Tunneling Protocol (SSTP) Remote Code Execution Vulnerability

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Microsoft Windows remote code execution issue in Secure Socket Tunneling Protocol. If an affected system exposes SSTP and an attacker meets the high-complexity conditions, the impact could include full loss of confidentiality, integrity, and availability. Microsoft lists an official remediation, and no provided source cites active exploitation.

Executive priority

Treat this as high priority for Windows VPN or externally reachable SSTP environments. It is not KEV-listed in the provided evidence, but the potential impact is severe enough to justify prompt patch validation.

Technical view

CVE-2022-34714 is a Windows SSTP RCE vulnerability with CVSS 3.1 score 8.1. The vector is network-accessible, unauthenticated, no user interaction, high attack complexity, unchanged scope, and high CIA impact. The source bundle maps it to CWE-94 and lists multiple Windows client and server versions as affected.

Likely exposure

Exposure is most relevant to listed Microsoft Windows versions where SSTP is enabled or reachable. Prioritize internet-facing VPN or tunneling infrastructure, Windows Server systems, and legacy Windows versions named in the affected list.

Exploitation context

The provided data marks KEV as false and CVSS exploit maturity as unproven. No supplied source confirms active exploitation. Attack complexity is high, but successful exploitation would have severe system-level consequences.

Researcher notes

Evidence is limited to CVE, CVE List, and MSRC metadata. The bundle does not include exploit details, proof-of-concept status, or workaround specifics. Avoid assuming affected configurations beyond Microsoft Windows SSTP exposure and the listed products.

Mitigation direction

  • Apply the Microsoft official remediation for each affected Windows version.
  • Use the MSRC advisory to identify the correct security update or servicing path.
  • Reduce SSTP exposure until patched where business operations allow.
  • Upgrade or isolate unsupported affected Windows versions lacking current servicing.
  • Track remediation completion for internet-facing and VPN-related systems first.

Validation and detection

  • Inventory Windows versions against the affected product list in the source bundle.
  • Identify systems where SSTP is enabled, exposed, or part of VPN services.
  • Confirm applicable Microsoft security updates are installed from official guidance.
  • Check external exposure records for SSTP-related public-facing systems.
  • Document exceptions and compensating controls for systems not immediately patchable.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2022-34714 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS: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 score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2022-34714Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 180910.0.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows 10 Version 21H110.0.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows 10 Version 20H210.0.0Listed
MicrosoftWindows Server version 20H210.0.0Listed
MicrosoftWindows 11 version 21H210.0.0Listed
MicrosoftWindows 10 Version 21H210.0.19043.0Listed
MicrosoftWindows 10 Version 150710.0.10240.0Listed
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows 76.1.0Listed
MicrosoftWindows 7 Service Pack 16.1.0Listed
MicrosoftWindows 8.16.3.0Listed
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0Listed
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0Listed
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

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.