CVE-2022-34722
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 Internet Key Exchange (IKE) Protocol Extensions 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 · high confidenceThis is a critical remote code execution vulnerability in Windows Internet Key Exchange (IKE) Protocol Extensions. An unauthenticated remote attacker can send specially crafted IKE packets to affected Windows systems to execute arbitrary code with elevated privileges, likely due to improper validation of IKE protocol messages.
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= 1607= 1809all versionsall versionsall versionsall versionsall versions= r2all versions= r2all 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Check Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build numberAffected if version matches any affected Windows 10, 11, 7, 8.1, Rt 8.1, Server 2008, 2012, or 2016 release
-
Verify IKE protocol is enabledCheck if Routing and Remote Access (RRAS) or VPN services are configured: run 'netsh interface show interface' and look for VPN or RAS interfaces, or check 'services.msc' for 'Routing and Remote Access' service statusAffected if IKE/IPSec VPN or RRAS is enabled and configured on the system
-
Confirm IKE ports are listeningRun 'netsh advfirewall firewall show rule name=all' or use 'netstat -an | findstr ":500 "' and 'netstat -an | findstr ":4500 "' to check if UDP ports 500 and 4500 are open and listeningAffected if UDP ports 500 (IKE) and 4500 (NAT-T) are listening and accessible on the system
-
Check VPN server role installationOn Server systems, check if 'Remote Access' server role is installed via Server Manager or run 'Get-WindowsFeature -Name RemoteAccess' in PowerShellAffected if Remote Access server role with IKE is installed and running
System is affected if it runs a vulnerable Windows version listed in the CVE and has IKE protocol enabled (VPN/RRAS configured) with ports 500/4500 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 CVE-2022-34722 immediately. As an interim control, block IKE protocol traffic (UDP ports 500 and 4500) at network perimeter firewalls for external traffic until patches can be deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34722 — 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-34722 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