Loading vulnerability…
CVE-2024-21305 is a security feature bypass vulnerability affecting Microsoft Windows Hypervisor-Protected Code Integrity (HVCI). HVCI is a virtualization-based security mechanism intended to enforce code integrity protections in the operating system. A successful exploit allows an attacker to bypass this protection mechanism, weakening the integrity enforcement that HVCI is designed to provide. Specific technical details about the vulnerable component or function are not available in the provided information.
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 detailed report and proof-of-concept (PoC) exploit for CVE-2024-21305, a vulnerability in Microsoft's Hypervisor-Protected Code Integrity (HVCI) on Windows 10 (builds 10.0.22621.1928 and 10.0.22621.1992) running on Intel hardware with VT-d enabled. The vulnerability allows arbitrary kernel-mode code execution in the root partition by exploiting writable and executable (W+X) guest physical memory regions, bypassing HVCI protections. The repository structure includes: - Documentation and a technical report (README.md, Report/README.md) explaining the vulnerability, exploitation steps, and expected/actual results. - A PoC kernel driver (Report/wx/wx/driver.cpp, Report/wx/wx/source.asm) that remaps a function pointer to a W+X memory page, writes shellcode, and triggers code execution. - A user-mode application (Report/wx/beep/beep.cpp) that calls the vulnerable function to execute the shellcode. - Build files for Visual Studio projects and solutions. The exploit is highly targeted and requires specific system configuration, including the ability to load unsigned drivers. The PoC demonstrates successful exploitation by causing a system crash with registers set to a known value, confirming arbitrary code execution in kernel mode. No network or remote attack vector is present; exploitation is purely local and requires administrative privileges.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.