dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-34714

HIGH · 8.1 CVSS v3.1 Published 2022-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Windows Secure Socket Tunneling Protocol (SSTP) contains a remote code execution vulnerability that allows an attacker to execute arbitrary code on affected Windows systems via specially crafted SSTP packets. SSTP is Microsoft's VPN protocol that tunnels PPP traffic over HTTPS. The high CVSS score indicates the vulnerability is remotely exploitable and can lead to complete system compromise.

MitigationApply the relevant Microsoft security update for CVE-2022-34714 through Windows Update or WSUS. Prioritize patching internet-facing Windows servers and workstations that terminate SSTP VPN connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 1607= 1809
Windows 11Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions= 20h2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Windows version is in affected range
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number
    Affected if The version matches any of the affected products listed (Windows 10 all versions, Windows 11 all versions, Windows 7 all versions, Windows 8.1 all versions, Windows Rt 8.1, Windows Server 2008/2008 R2, Windows Server 2012/2012 R2, Windows Server 2016 all versions)
  2. Determine if SSTP feature is installed
    Run 'Get-WindowsOptionalFeature -Online -FeatureName SstpSvc' in PowerShell to check if the SSTP service feature is present on the system
    Affected if The feature state shows as Enabled or Available, indicating SSTP is installed on the system
  3. Check if SSTP service is running
    Run 'Get-Service -Name SstpSvc' or 'sc query SstpSvc' to check the status of the Secure Socket Tunneling Protocol service
    Affected if The service exists and shows a status of Running on the target system
  4. Check for recent security updates
    Run 'Get-HotFix | Where-Object {$_.Description -like "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recently installed security patches, or specifically search for KB5015861 (the patch for this CVE)
    Affected if The security update for CVE-2022-34714 is NOT installed (patch missing)

The system is vulnerable if it runs an affected Windows version with SSTP feature enabled and is missing the relevant security update for CVE-2022-34714.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Microsoft security update for CVE-2022-34714 through Windows Update or WSUS. Prioritize patching internet-facing Windows servers and workstations that terminate SSTP VPN connections.

Recommended fix Moderate confidence
  1. Open Windows Update on the affected system (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to download and install all available security updates
  3. Ensure the Windows Secure Socket Tunneling Protocol (SSTP) related security update is installed
  4. Restart the system if prompted to complete the installation
  5. Verify the update was successfully installed by checking Windows Update history

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34714 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data