Malicious VNC Servers Overflow TightVNC and UltraVNC Viewers
A crafted JPEG update can corrupt a Windows viewer's heap. Upgrade UltraVNC to a current fixed release; replace affected TightVNC viewers.

A malicious VNC server can corrupt the heap of a Windows viewer simply by sending it a crafted screen update. The CERT/CC vulnerability note names TightVNC Windows Viewer 1.3.10 and affected UltraVNC Windows Viewers. In testing, the overflow crashed the viewer; code execution with the viewer user’s privileges is a possible consequence of the memory corruption, not a demonstrated outcome.
The CVE Program record scopes the affected UltraVNC versions to 1.8.2.4 through 1.8.2.6 and lists TightVNC 1.3.10. This is a client-side exposure: an administrator opening a remote desktop session is the person whose viewer processes the server’s image. The server can be attacker-operated or a familiar server that has been compromised.
A JPEG row overruns the viewer buffer
VNC viewers receive screen rectangles through the Remote Framebuffer protocol. The Tight encoding can carry compressed JPEG image data. CERT/CC describes a mismatch inside DecompressJpegRect(): the Windows viewer allocates a heap buffer with a hardcoded maximum row width of 8,192 pixels, then converts pixels using the rectangle width supplied by the server. If that width exceeds what the allocation holds, conversion writes beyond the buffer.
The server can also advertise a framebuffer large enough to contain its rectangle. A bounds check against that advertised screen size alone therefore leaves the local allocation exposed. Even when staff only initiate outbound VNC sessions, the server’s crafted screen update reaches their local viewer. As CERT/CC puts it, “Authentication or transport encryption does not prevent exploitation by a malicious server participating in the session.” Those protections secure the connection and authenticate its other end; they do not change how the viewer sizes its JPEG conversion buffer.
The server controls the dangerous width
An operator may know which VNC servers staff normally use, but server familiarity is a weaker safeguard if one of those systems is compromised. The attack requires the viewer to connect and process the crafted update.
CERT/CC credits re9rch for reporting the vulnerability. Its UltraVNC vendor statement describes changing buffer sizing to match the JPEG row width and rejecting out-of-range rectangle dimensions. The CERT/CC note says UltraVNC addressed this flaw in 1.8.2.8 and recommends a current supported release containing the fix, such as 1.8.3.1. CERT/CC says it could not reach TightVNC to coordinate a fix for the affected 1.3.10 Windows viewer; treat that version as needing replacement with a maintained viewer confirmed to address the problem.
Check viewers before the next session
Inventory the Windows workstations and jump hosts that open VNC sessions. Read the installed viewer version on each: move affected UltraVNC installations to a current supported release containing the fix, such as 1.8.3.1, and replace affected TightVNC 1.3.10 Windows viewers with a maintained alternative whose fix you can confirm. Check the version installed on each workstation even after software distribution reports a completed job.
Until those changes land, limit viewer connections to trusted servers in the client configuration and through the approved remote-access workflow. This reduces contact with attacker-operated servers; a compromised trusted server can still send the bad update. Verify the rollout by checking the installed versions on affected endpoints and confirming that the TightVNC viewer is gone before staff resume those sessions. A viewer crash can have many causes, so preserve the session destination, time, and local crash evidence if an unexpected VNC session fails.