Loading vulnerability…
CVE-2019-0803 is a local elevation-of-privilege vulnerability in Microsoft Windows caused by improper handling of objects in memory by the Win32k component. Successful exploitation allows code execution in kernel mode. Public proof-of-concept exploits exist, and exploitation has been observed in Tonto Team operations and SLUB malware. The vulnerability is also associated with known ransomware campaign use. The precise vulnerable function and affected Windows release ranges are currently not available.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a proof-of-concept (PoC) exploit for CVE-2019-0803, a Win32k Elevation of Privilege vulnerability affecting Microsoft Windows 7 SP1. The structure consists of a Visual Studio solution with project files and a header file (struct.h) that defines various Windows internal structures and constants used in the exploit. The README indicates the exploit's purpose is to steal a security token, allowing local privilege escalation. The exploit must be compiled and run locally on a vulnerable Windows 7 SP1 system. No network or remote attack vector is present; the attack is purely local. The repository references a related exploit for CVE-2016-7255 for further context. The main exploit logic is likely implemented in the (not provided) main.cpp and DDE.cpp files, with struct.h providing necessary data structures for interacting with Windows internals.
This repository is a proof-of-concept (PoC) exploit for CVE-2019-0803, a Win32k Elevation of Privilege vulnerability affecting Microsoft Windows 7 SP1. The exploit is implemented as a Visual Studio C++ project, with the main code files (such as main.cpp, DDE.cpp, and struct.h) located under win7sp1/poc_test/. The struct.h file defines various Windows kernel structures and constants used for the exploit, including those related to window management and process tokens. The README.md provides a brief description, a screenshot link, and a reference to a related exploit (CVE-2016-7255). The exploit's main capability is to locally escalate privileges by stealing a security token, allowing the attacker to gain elevated access on a vulnerable system. No network or remote attack vectors are present; the exploit must be run locally. The repository is structured as a standard Visual Studio project, and the exploit is at the proof-of-concept stage, requiring manual compilation and execution.
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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Windows privilege escalation vulnerability reportedly used by Kingminer during infection to gain elevated privileges and hinder defensive intervention.
A local privilege escalation vulnerability targeted with publicly available exploit tools during the campaign. The observed activity involved attempts to elevate privileges on compromised IIS servers.
A vulnerability exploited by Tonto Team for privilege escalation.
A specific vulnerability (CVE-2019-0803) referenced as being exploited by the SLUB loader in a 2019 campaign; the content does not provide technical details beyond noting exploitation and its use in the malware delivery chain.
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.