Proxy Server CCProxy buffer overflow
| proxy-server-ccproxy-bo (18012) |  High Risk |
Description:
Proxy Server CCProxy is vulnerable to a buffer overflow, caused by improper bounds checking when handling HTTP requests. By sending a specially-crafted long HTTP GET request to CCProxy, a remote attacker could overflow a buffer and execute arbitrary code on the system or cause a denial of service.
Platforms Affected:
- Youngzsoft, CCProxy 6.61
Remedy:
Upgrade to the latest version of CCProxy (6.2 or later), when it becomes available from the Proxy Server CCProxy Web page. See References.
Consequences:
Gain Access
References:
- Proxy Server CCProxy Web page, CCProxy - Proxy Server Software for Windows at http://www.youngzsoft.net/ccproxy/.
- Securiteam Mailing List Security Holes & Exploits 11/9/2004, CCProxy Log Stack Overflow at http://www.securiteam.com/exploits/6E0032KBPM.html.
- BID-11666: Youngzsoft CCProxy Logging Function Unspecified Remote Buffer Overflow Vulnerability
- CVE-2004-2416: Buffer overflow in the logging component of CCProxy allows remote attackers to execute arbitrary code via a long HTTP GET request.
- CVE-2004-2685: Buffer overflow in YoungZSoft CCProxy 6.2 and earlier allows remote attackers to execute arbitrary code via a long address in a ping (p) command to the Telnet proxy service, a different vector than CVE-2004-2416.
- OSVDB ID: 11593: CCProxy GET Request Overflow
- SA13085: CCProxy Multiple Buffer Overflow Vulnerabilities
- SECTRACK ID: 1012189: CCProxy Buffer Overflow in Logging Function Lets Remote Users Execute Arbitrary Code
Reported:
Nov 09, 2004
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net