1-minute read of a 3 min report

Malicious VNC Servers Overflow TightVNC and UltraVNC Viewers

By

1-minute read

What a defender needs to know

A malicious VNC server can send a crafted Tight JPEG screen update that overruns a Windows viewer’s heap buffer. CERT/CC identifies TightVNC Windows Viewer 1.3.10 and affected UltraVNC Windows Viewers; the CVE record lists UltraVNC 1.8.2.4 through 1.8.2.6. CERT/CC reproduced a viewer crash. Code execution with the viewer user’s privileges is a possible memory-corruption impact, rather than an outcome demonstrated in its testing.

In DecompressJpegRect(), the viewer allocates for a hardcoded 8,192-pixel row but converts JPEG data across a server-supplied rectangle width. The server can advertise a framebuffer large enough to pass a screen-size check. Authentication and encryption of the session do not stop a malicious participating server from supplying that update.

Identify Windows workstations and jump hosts running these viewers. Upgrade affected UltraVNC installations to a current supported release containing the fix, such as 1.8.3.1; CERT/CC identifies 1.8.2.8 as the first release addressing the flaw. Replace affected TightVNC 1.3.10 Windows viewers with a maintained alternative confirmed to address it. Until rollout finishes, restrict client connections to trusted VNC servers, while accounting for the risk from a compromised trusted server. After rollout, read the installed viewer version on each endpoint and confirm the affected TightVNC viewer has been removed before those users reconnect.

Primary sources