A privilege escalation vulnerability in the Windows kernel. Publicly available information here identifies the issue only at a high level and does not provide sufficient technical detail about the vulnerable component, code path, or triggering condition to accurately describe the underlying flaw mechanism.
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) local denial-of-service exploit for CVE-2024-20698, a vulnerability in the Windows kernel (ntoskrnl.exe) related to the WbAddLookupEntryEx function. The exploit consists of two main C++ programs: 'DoS_exploit' and 'NtQuerySysInfo_test'. 'DoS_exploit' attempts to create an extremely large number of concurrent processes, each running 'NtQuerySysInfo_test.exe'. The test executable calls the NtQuerySystemInformation API with a specific argument (0xB9), which triggers the vulnerable code path in the kernel. The exploit aims to cause an integer overflow during memory allocation in the kernel, leading to memory corruption and potential system instability or crash. The README provides a detailed technical analysis of the vulnerability, the patch, and the exploit strategy. The exploit is limited by the system's ability to create a massive number of processes, which may not be feasible on all systems, but demonstrates the vulnerability's impact. No network or remote attack vector is present; this is a local privilege exploit requiring code execution on the target system.
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.