Loading vulnerability…
CVE-2008-0610 is a stack-based buffer overflow in the UltraVNC viewer (vncviewer) affecting UltraVNC 1.0.2 and 1.0.4 prior to 01252008. The flaw is in ClientConnection::NegotiateProtocolVersion (vncviewer/ClientConnection.cpp), where a modified size value can trigger an out-of-bounds write on the stack during protocol version negotiation. Exploitation can lead to remote code execution or a crash (denial of service). The issue is reachable when the viewer is in LISTENING mode or when using the DSM plugin.
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/ultravnc_viewer_bof.rb) that exploits a buffer overflow vulnerability (CVE-2008-0610) in UltraVNC Viewer 1.0.2 (vncviewer.exe) on Windows XP SP3. The exploit works by acting as a malicious VNC server, listening on TCP port 5900. When a vulnerable UltraVNC client connects, the server sends a specially crafted protocol version and payload that triggers a stack buffer overflow in the client, allowing arbitrary code execution. The module allows the attacker to deliver a customizable Metasploit payload (up to 500 bytes). The exploit is operational and requires the victim to initiate a connection to the attacker's server. The code is written in Ruby and is structured as a standard Metasploit exploit module, making use of the Msf::Exploit::Remote::TcpServer mixin.
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.