A local privilege escalation vulnerability exists in RealVNC VNC Server versions 6.9.0 through 5.1.0 for Windows. The vulnerability arises because the installer repair operation executes files from the %TEMP% directory with SYSTEM privileges. An attacker with local access can place a malicious executable in %TEMP% prior to a repair operation, resulting in arbitrary code execution as SYSTEM.
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-2022-27502, a DLL hijacking vulnerability in RealVNC Server up to version 6.9.0 on Windows. The exploit is implemented as a malicious DLL (adsldpc.dll) written in C++. When the DLL is placed in the %TEMP% directory and a repair operation of RealVNC Server is triggered, the DLL is loaded and executes an arbitrary system command (by default, 'whoami'), writing the output to %TEMP%\output.txt. The command to be executed can be changed by modifying line 191 of dllmain.cpp. The repository includes Visual Studio project files, build logs, and the main exploit code in adsldpc/dllmain.cpp. The attack vector is local, requiring the attacker to place the DLL and trigger the repair process. The exploit targets Windows systems running vulnerable versions of RealVNC Server.
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.