PHP-Nuke HTTP response splitting
| php-nuke-http-response-splitting (20116) |  Medium Risk |
Description:
PHP-Nuke is vulnerable to an HTTP response-splitting attack. A remote attacker could create a specially-crafted HTTP request containing an invalid HTTP header to cause the server to return a split response. This would allow the attacker to obtain sensitive information or to perform further attacks on the system such as Web cache poisoning or cross-site scripting.
Platforms Affected:
- PHP-Nuke, PHP-Nuke 7.0
- PHP-Nuke, PHP-Nuke 7.1
- PHP-Nuke, PHP-Nuke 7.2
- PHP-Nuke, PHP-Nuke 7.3
- PHP-Nuke, PHP-Nuke 7.4
- PHP-Nuke, PHP-Nuke 7.5
- PHP-Nuke, PHP-Nuke 7.6
Remedy:
No remedy available as of July 4, 2009.
Consequences:
Obtain Information
References:
- BugTraq Mailing List, Fri Apr 15 2005 - 22:30:18 CDT , Http Response Splitting Vulnerability In PHP-NUKE 7.6 and below at http://archives.neohapsis.com/archives/bugtraq/2005-04/0237.html.
- HTTP RESPONSE SPLITTING, DCrab's advisory- PHP-Nuke HTTP RESPONSE SPLITTING at http://www.security.nnov.ru/Idocument356.html.
- PHP-NUKE, PHP-NUKE the future of the web.. at http://phpnuke.org/.
- BID-13201: PHP-Nuke Surveys Module HTTP Response Splitting Vulnerability
- CVE-2005-1180: HTTP Response Splitting vulnerability in the Surveys module in PHP-Nuke 7.6 allows remote attackers to spoof web content and poison web caches via hex-encoded CRLF (%0d%0a) sequences in the forwarder parameter.
- OSVDB ID: 15647: PHP-Nuke modules.php forwarder Parameter Header/Body XSS
- SA14965: PHP-Nuke "forwarder" Parameter HTTP Response Splitting
Reported:
Apr 13, 2005
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