dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-35767

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

This is a remote code execution vulnerability in Windows Secure Socket Tunneling Protocol (SSTP), a VPN protocol that uses SSL/TLS. An unauthenticated attacker could exploit this to execute arbitrary code on affected Windows systems via specially crafted SSTP packets.

MitigationApply the relevant Microsoft security updates for CVE-2022-35767 to all affected Windows systems. Prioritize internet-facing Windows servers running SSTP services.

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. Verify SSTP service is enabled
    Open Services console (services.msc) and look for 'Routing and Remote Access' service, or check for 'SstpSvc' service. Alternatively, run 'Get-Service SstpSvc' in PowerShell if available, or check Windows Features for 'Routing and Remote Access' (RRAS) which includes SSTP.
    Affected if SSTP service is installed and running on the system
  2. Confirm Windows version falls within affected range
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version. Compare against the affected list: Windows 10 (all versions, specifically 1607, 1809, 20h2, 21h1, 21h2), Windows 11 (all versions), Windows 7 (all versions), Windows 8.1 (all versions), Windows Rt 8.1 (all versions), Windows Server 2008/2008 R2, Windows Server 2012/2012 R2, Windows Server 2016 (all versions, specifically 20h2).
    Affected if The installed Windows version matches any of the affected versions listed in the CVE
  3. Check if SSTP VPN is configured
    Review existing VPN connections: open Network Connections (ncpa.cpl) or run 'Get-VpnConnection' in PowerShell. Look for VPN connections using SSTP protocol. Also check RAS phonebook entries if accessible.
    Affected if An SSTP-based VPN connection exists or is configured on the system
  4. Verify security update installation
    Check for installed updates: run 'wmic qfe list' or 'Get-HotFix | Sort-Object InstalledOn' and look for the Microsoft security update for CVE-2022-35767 (typically released August 2022). The specific KB varies by Windows version.
    Affected if The system is missing the security update for CVE-2022-35767 and meets the version and SSTP criteria above

A system is affected if it runs any of the listed Windows versions, has SSTP service enabled or configured, and is missing the CVE-2022-35767 security update.

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 updates for CVE-2022-35767 to all affected Windows systems. Prioritize internet-facing Windows servers running SSTP services.

Recommended fix Moderate confidence

Apply the August 2022 Microsoft security updates for your specific Windows version

  1. Apply the Microsoft security update for CVE-2022-35767. This vulnerability was addressed in the August 2022 Microsoft security updates.
  2. Open Windows Update and check for available updates, or manually download the security update from the Microsoft Update Catalog.
  3. Install all applicable updates for your Windows version, particularly updates related to the Secure Socket Tunneling Protocol (SSTP).
  4. Restart the system after applying the updates to ensure the vulnerability is mitigated.
  5. Verify the update was successfully installed by checking the installed updates list or using the Windows Update history.
Caveat Standard patching risks apply - ensure backups are in place before applying updates in production environments

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-35767 — 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-35767 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