CVE-2022-34718
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 TCP/IP 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 confidenceWindows TCP/IP remote code execution vulnerability in the IPsec driver (ipsec.sys) allowing unauthenticated attackers to execute arbitrary code via specially crafted IPsec 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 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.
-
Identify Windows version and buildRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the installed Windows version and build numberAffected if The version matches Windows 10 (any build), Windows 11 (any build), Windows 8.1, Windows Rt 8.1, Windows 7, or Windows Server 2008/2012/2016 (any build)
-
Verify IPsec service is runningRun 'services.msc' and look for 'IKE and AuthIP IPsec Keying Modules' service, or run 'sc query IKEEXT' from command promptAffected if The IKEEXT service is running or set to auto-start (indicates IPsec keying is enabled)
-
Check if IPsec policy is appliedRun 'netsh ipsec dynamic show all' or 'netsh ipsec static show all' to list active IPsec policiesAffected if Any IPsec policies or tunnels are configured and active
-
Confirm security update is installedRun 'systeminfo | findstr "KB"' or 'Get-HotFix | Where-Object {$_.HotFixID -like "KB5015857" -or $_.HotFixID -like "KB5015871"}' to check for August 2022 patchesAffected if Neither KB5015857 nor KB5015871 (nor subsequent relevant patches) appear in the installed updates list
The system is vulnerable if it runs an affected Windows version, has IPsec/IKEEXT enabled or configured, and is missing the August 2022 security updates.
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 Microsoft security updates released August 2022 (KB5015857, KB5015871, or subsequent patches) to address the vulnerability in Windows TCP/IP stack.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34718 — 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-34718 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