Blue Coat WinProxy Telnet Proxy Can Be Crashed By Remote Users
SecurityTracker Alert ID: 1015442|
SecurityTracker URL: http://securitytracker.com/id/1015442
(Links to External Site)
Date: Jan 5 2006
Denial of service via network|
Fix Available: Yes Vendor Confirmed: Yes Exploit Included: Yes |
iDEFENSE reported a vulnerability in Blue Coat WinProxy in the telnet proxy. A remote user can cause denial of service conditions.|
A remote user can send a long string of 0xFF characters to the target telnet proxy service to trigger a heap error and cause the WinProxy service to crash.
The vendor was notified on November 15, 2005.
The original advisory is available at:
A remote user can cause the target service to crash.|
The vendor has issued a fixed version (6.1a).|
Vendor URL: www.winproxy.com/index.asp (Links to External Site)
Source Message Contents
Date: Thu, 05 Jan 2006 16:33:09 -0500|
Subject: iDefense Security Advisory 01.05.06: Blue Coat WinProxy Telnet DoS
Blue Coat WinProxy Telnet DoS Vulnerability
iDefense Security Advisory 01.05.06
January 05, 2006
BlueCoat WinProxy is an Internet sharing proxy server designed for small
to medium businesses. In addition to Internet sharing Winproxy also
hosts a series of security, anti-spam and anti-spyware capabilities.
More information can be located from the vendors site at:
Remote exploitation of a design error in Blue Coat Systems Inc.'s
WinProxy allows attackers to cause a denial of service (DoS) condition.
The vulnerability can be triggered by sending a large string of 0xFF
characters to the telnet proxy port of the server. Sending such a string
will cause a heap corruption in the Winproxy process causing it to
Successful exploitation requires an attacker to send a stream of TCP
packets containing the 0xFF character to the WinProxy telnet server on
TCP port 23. This will lead to a crash of the server and it will be
unusable until it is restarted.
In lab tests, the heap corruption caused by this exploit led to cashes
in random locations in the process. The possibility for remote code
execution is possible, however will likely be very hard to control and
maintain reliable code execution.
iDefense has confirmed this vulnerability in WinProxy 6.0.
All previous versions are suspected to be vulnerable.
Disabling the WinProxy telnet protocol will prevent this attack.
VI. VENDOR RESPONSE
Blue Coat has released WinProxy 6.1a to address this vulnerability.
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CAN-2005-3654 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org), which standardizes names for
VIII. DISCLOSURE TIMELINE
11/15/2005 Initial vendor notification
11/15/2005 Initial vendor response
01/05/2006 Coordinated public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
Copyright © 2006 iDefense, Inc.
Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDefense. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically, please
email firstname.lastname@example.org for permission.
Disclaimer: The information in the advisory is believed to be accurate
at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct, indirect,
or consequential loss or damage arising from use of, or reliance on,
To unsubscribe, go here: