Loading vulnerability…
CVE-2024-1305 is a memory corruption vulnerability in the Windows tap-windows6 driver version 9.26 and earlier. The flaw is caused by improper validation of size-related data for incoming write operations, specifically involving the PacketLength and PrefixLength parameters in the TapDeviceWrite method. By supplying crafted input that is not correctly bounds-checked, an attacker can trigger a buffer overflow in kernel context. The vulnerability can lead to a system bug check and, under favorable conditions, arbitrary code execution in kernel space.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in the tap-windows6 driver caused by improper validation of PacketLength and PrefixLength in TapDeviceWrite, which can lead to buffer overflow and remote code execution.
A memory overflow vulnerability in the OpenVPN Windows TAP driver that can cause denial-of-service.
Kernel memory corruption in tap-windows6 driver (<= 9.26) due to insufficient bounds checking on write operations, potentially leading to kernel code execution.
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.