Pavuk Location: buffer overflow
| pavuk-location-bo (16551) |  High Risk |
Description:
Pavuk is vulnerable to a stack-based buffer overflow, caused by improper bounds checking in the Location: header. By sending a specially-crafted Location: header in a '305 Use Proxy' HTTP Status Code, a remote attacker, in control of a malicious Web server, could overflow a buffer and execute arbitrary code on the vulnerable system.
Consequences:
Gain Access
Remedy:
Upgrade to the latest version of Pavuk (0.9.28-r2 or later), available from the Pavuk Web site. See References.
For Debian GNU/Linux 3.0 (alias woody):
Upgrade to the latest Pavuk package (0.9pl28-1 or later), as listed in DSA-527-1. See References.
For Gentoo Linux:
Upgrade to the latest version of Pavuk (0.9.31 or later), as listed in GLSA 200411-19. See References.
For other distributions:
Contact your vendor for upgrade or patch information.
References:
- Full-Disclosure Mailing List, Thu Jul 01 2004 - 17:48:20 CDT: pavuk buffer overflow.
- Pavuk Web site: Pavuk.
- BID-10633: Pavuk Remote Stack-Based Buffer Overrun Vulnerability
- BID-11626: Pavuk Multiple Unspecified Remote Buffer Overflow Vulnerabilities
- CVE-2004-0456: Stack-based buffer overflow in pavuk 0.9pl28, 0.9pl27, and possibly other versions allows remote web sites to execute arbitrary code via a long HTTP Location header.
- DSA-527: pavuk -- buffer overflow
- GLSA-200406-22: Pavuk: Remote buffer overflow
- GLSA-200411-19: Pavuk: Multiple buffer overflows
Platforms Affected:
- Debian Debian Linux 3.0
- Gentoo Linux
- Pavuk Pavuk 0.9.28-rl and prior
Reported:
Jun 30, 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