Loading vulnerability…
CVE-2020-1034 is an elevation of privilege vulnerability in the Windows Kernel, caused by improper handling of objects in memory. A locally authenticated attacker can exploit this flaw by running a specially crafted application, allowing them to execute code with elevated permissions. The vulnerability is addressed by correcting the way the Windows Kernel manages memory objects.
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 is a Proof-of-Concept (PoC) exploit for CVE-2020-1034, a local privilege escalation vulnerability in Microsoft Windows 10 (specifically version 2004, build 19041.488). The repository is structured as a Visual Studio solution with three main components: - `exploit_part_1/` and `exploit_part_2/` each contain a Main.cpp file implementing different stages or variants of the exploit. Both parts focus on manipulating Windows process tokens to escalate privileges from a normal user to SYSTEM by leveraging the vulnerable behavior described in CVE-2020-1034. The exploit achieves this by locating and modifying the process token, then spawning a new command shell (`cmd.exe`) as SYSTEM. - `pool_address_leak/` contains code to leak kernel pool addresses, which is often a prerequisite for reliable exploitation of kernel vulnerabilities. - `Utils/` provides shared header files and project configuration files used by the exploit code. The exploit requires local access to a vulnerable, unpatched Windows 10 system. It does not use any network or remote attack vectors. The main fingerprintable endpoint is the use of `c:\windows\system32\cmd.exe` as the payload. The code is written in C++ and is intended for research and demonstration purposes, as indicated by the README and the structure of the code. The exploit is not weaponized or part of a framework, but provides a clear demonstration of the vulnerability and its exploitation process.
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.