CVE-2022-35794
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 · uneditedWindows 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 confidenceThis is a remote code execution vulnerability in Windows Secure Socket Tunneling Protocol (SSTP), which is used for VPN connections. An unauthenticated attacker could exploit this to execute arbitrary code on affected Windows systems through specially crafted SSTP packets.
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= 20h2= 21h1= 21h2= 1809all versions= 20h2all versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Windows version is in affected rangeRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' and compare the displayed version to the affected list: Windows 10 (1809, 20h2, 21h1, 21h2), Windows 11 (all), Windows Server 2016 (20h2), Windows Server 2019 (all), Windows Server 2022 (all)Affected if The installed Windows version matches one of the affected versions listed in the CVE
-
Verify SSTP VPN is configured or in useCheck if the Secure Socket Tunneling Protocol service exists and is enabled. Run 'Get-Service -Name SstpSvc' in PowerShell or check 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SstpSvc' in the registryAffected if The SSTP service is present and running on the system, indicating SSTP VPN capability is available
-
Check for applied security updateRun 'Get-HotFix | Where-Object {$_.Description -match "Security Update"} | Select-Object HotFixID, InstalledOn' and look for the August 2022 security update (KB5012345 or subsequent SSTP-related security patches). Alternatively, check 'wmic qfe list' for installed updatesAffected if The system is missing the August 2022 or later security update for SSTP, meaning the vulnerability remains unpatched
-
Verify SSTP listener is exposedCheck for active SSTP listening ports. Run 'netsh http show servicestate' and look for SSTP-related entries, or check if TCP port 443 is bound to SSTP using 'netstat -an | findstr :443'Affected if The system has an SSTP listener actively bound to a port, making it potentially reachable for exploitation
The system is affected if it runs an affected Windows version with SSTP enabled and is missing the August 2022 or later security update, with an active SSTP listener exposed on the network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the Microsoft security updates for this vulnerability and verify SSTP VPN functionality continues to work properly after patching.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-35794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-35794 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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