CVE-2022-41090
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 Point-to-Point Tunneling Protocol Denial of Service 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 confidenceA denial of service vulnerability exists in Windows Point-to-Point Tunneling Protocol (PPTP). An unauthenticated attacker could send specially crafted network packets to trigger the condition, causing the affected system to stop responding until restarted.
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 dataall versions= 20h2= 21h1= 21h2= 22h2= 1607= 1809all versions= 22h2all versionsall versions= r2all versions= r2all 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build numberAffected if The version matches any of the affected products listed (Windows 10 versions 20h2, 21h1, 21h2, 22h2, 1607, 1809; Windows 11 version 22h2; Windows 7; Windows 8.1; Windows Server 2008 R2; Windows Server 2012/2012 R2; Windows Server 2016; Windows Server 2019)
-
Check if Routing and Remote Access service is runningRun 'sc query RemoteAccess' or 'Get-Service RemoteAccess' to query the RRAS service statusAffected if The service state is RUNNING - PPTP functionality is active and the system could be vulnerable if a malicious packet is received
-
Check for PPTP listening portRun 'netstat -an | findstr "1723"' or 'Get-NetTCPConnection -LocalPort 1723' to detect if PPTP port TCP 1723 is listeningAffected if Port 1723 is in LISTENING or ESTABLISHED state - the PPTP server is actively listening and could receive malicious packets
-
Verify PPTP miniport driver loadedRun 'netsh interface show interface' to list all RAS interfaces, or check Device Manager for 'WAN Miniport (PPTP)' under Network AdaptersAffected if A PPTP miniport interface exists and is enabled - the vulnerable PPTP protocol driver is present in the system
The system is affected if it runs an affected Windows version AND has PPTP (RRAS) service enabled or has PPTP ports listening, as the vulnerability triggers when specially crafted PPTP packets are received by the enabled PPTP service.
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 update for CVE-2022-41090 via Windows Update or deploy the corresponding KB patch from Microsoft's security bulletin.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41090 — 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-41090 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