Vulnerability Note VU#598581

AT&T WinVNC server contains buffer overflow in Log.cpp

Original Release date: 28 Jun 2001 | Last revised: 28 Jun 2001

Overview

A buffer overflow in the WinVNC server on Windows systems can allow an intruder to gain control of the VNC server and execute arbitrary code with the privileges of the user running the server.

Description

AT&T WinVNC is a free software package available from AT&T Labs Cambridge that allows users to interact with the desktop of a remote Windows host. By providing a specially crafted HTTP request to the VNC server, an attacker can overflow a buffer in Log.cpp, resulting in access to the VNC server and the ability to execute arbitrary code with the privileges of the user running the server. It is worth noting that the VNC server does not listen on 80/tcp by default. See the following url:

http://www.uk.research.att.com/vnc/faq.html#q52

Impact

Local and remote users can execute arbitrary code with the privileges of the user running the server.

Solution

Apply this patch while inside the vnc_winsrc/winvnc
directory:

--- Log.cpp Mon Jan 15 18:17:46 2001
+++ Log.cpp Mon Jan 15 18:18:31 2001
@@ -130,7 +130,7 @@

// - Write the log message
TCHAR line[LINE_BUFFER_SIZE];
- vsprintf(line, format, ap);
+ _vsnprintf(line, sizeof(line)-sizeof(TCHAR), format, ap);
ReallyPrintLine(line);
}

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
ATTAffected15 Jan 200115 Jun 2001
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

Our thanks to CORE SDI for the information contained in their bulletin.

This document was written by Ian A. Finlay and is based on information obtained from a Core SDI Security Advisory.

Other Information

  • CVE IDs: CAN-2001-0168
  • Date Public: 29 Jan 2001
  • Date First Published: 28 Jun 2001
  • Date Last Updated: 28 Jun 2001
  • Severity Metric: 12.60
  • Document Revision: 32

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.