Loading vulnerability…
CVE-2024-35264 is a remote code execution vulnerability affecting .NET 8 / ASP.NET Core 8 and associated Visual Studio development environments through a use-after-free condition in Kestrel HTTP/3 request handling. The flaw is triggered by data corruption arising from reuse of deallocated memory during request body processing. Available reporting indicates exploitation depends on a race condition that can be induced by interrupting or closing an HTTP/3 stream while the server is still processing the request body, leading to unsafe memory access and potential attacker-controlled code execution.
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.
Use-after-free remote code execution vulnerability affecting .NET and Visual Studio Code, exploitable by winning a race condition through interruption of an HTTP/3 stream during request body processing.
Remote code execution vulnerability in .NET and Visual Studio involving an HTTP/3 race condition.
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.