First published: Wed Feb 04 2009(Updated: )
Multiple integer signedness errors in (1) UltraVNC 1.0.2 and 1.0.5 and (2) TightVnc 1.3.9 allow remote VNC servers to cause a denial of service (heap corruption and application crash) or possibly execute arbitrary code via a large length value in a message, related to the (a) ClientConnection::CheckBufferSize and (b) ClientConnection::CheckFileZipBufferSize functions in ClientConnection.cpp.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
TightVNC | =1.3.9 | |
UltraVNC | =1.0.2 | |
UltraVNC | =1.0.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2009-0388 is classified as a medium severity vulnerability due to its potential for denial of service and arbitrary code execution.
To fix CVE-2009-0388, upgrade to the latest versions of UltraVNC and TightVNC that address these integer signedness errors.
The affected software includes UltraVNC versions 1.0.2 and 1.0.5, as well as TightVNC version 1.3.9.
The risks associated with CVE-2009-0388 include potential application crashes and the execution of arbitrary code on remote servers.
Yes, CVE-2009-0388 can be exploited remotely by sending crafted messages with large length values to the affected VNC servers.