Loading vulnerability…
A buffer overflow vulnerability exists in AT&T WinVNC (Virtual Network Computing) server versions 3.3.3r7 and earlier. The flaw is triggered when the server is configured with the DebugLevel registry key set to a value greater than 0, and a remote attacker sends a specially crafted, overly long HTTP GET request. This can result in the execution of arbitrary commands on the affected 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 single Metasploit module (modules/exploits/windows/vnc/winvnc_http_get.rb) that exploits a buffer overflow vulnerability (CVE-2001-0168) in the AT&T WinVNC web server (version <= 3.3.3r7) when debugging mode with logging is enabled. The exploit works by sending an overly long HTTP GET request to the web server (default port 5800), causing a stack overflow and allowing arbitrary code execution. The module supports multiple Windows targets (NT4, 2000, XP) with specific return addresses for each. The payload is customizable and can be any Metasploit-compatible payload up to 979 bytes, avoiding certain bad characters. The exploit is operational and requires the target to be in a non-default configuration (debugging mode with logging enabled). The only fingerprintable endpoint is the HTTP service on port 5800 of the target. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.