Loading vulnerability…
CVE-2020-0624 is an elevation of privilege vulnerability in the Windows Win32k component, which arises due to improper handling of objects in memory. The flaw allows a local attacker to execute arbitrary code with elevated privileges by exploiting the way Win32k 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 contains a proof-of-concept (POC) exploit for CVE-2020-0624, a use-after-free vulnerability in the Windows kernel component win32k. The main code file, 'cve-2020-0624.cpp', is a C++ program that manipulates the KernelCallbackTable in the Process Environment Block (PEB) of the current process to redirect kernel callback functions to attacker-supplied code. It then creates parent and child window objects and sends a message to trigger the vulnerability. The exploit is local-only and does not provide privilege escalation or a shell; its purpose is to demonstrate the existence of the vulnerability. The repository is structured as a Visual Studio C++ project, with one main code file and associated project files. No network or remote endpoints are present; the only fingerprintable endpoint is the use of the KernelCallbackTable in the PEB. The exploit is suitable for researchers or security analysts studying the vulnerability, and is not weaponized.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.