CVE-2022-34718 is a remote code execution vulnerability in the Windows TCP/IP stack. The vulnerability allows an unauthenticated attacker to send specially crafted IPv6 packets to a Windows host with the IPSec service enabled, potentially leading to arbitrary code execution in the context of the kernel. The flaw is due to improper handling of memory in the TCP/IP stack when processing certain network packets.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2022-34718, a remote code execution vulnerability in the IPv6 stack of Microsoft Windows systems. The main file, 'ipv6-rce-poc.py', is a Python script that uses the Scapy library to craft and send specially constructed IPv6 packets to a target address. The exploit works by sending fragmented IPv6 packets with specific routing and fragment headers, attempting to trigger the vulnerability on the target system. The script requires root privileges to send raw packets and is intended for use in a controlled environment (such as a virtual machine). The script does not provide a shell or execute arbitrary code on the target; instead, it detects whether the target is vulnerable by observing the system's response to the crafted packets. The repository includes a README with usage instructions, a requirements.txt specifying Scapy as a dependency, and standard project files (.gitignore, LICENSE). The only fingerprintable endpoint in the code is a DNS domain used for connectivity testing. Overall, this is a PoC exploit for vulnerability detection, not a weaponized exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.