GLSA Bodhisattva
Joined: 13 Jun 2003 Posts: 4087 Location: Dresden, Germany
|
Posted: Thu Jul 15, 2004 2:22 pm Post subject: [ GLSA 200407-13 ] PHP: Multiple security vulnerabilities |
|
|
Gentoo Linux Security Advisory
Title: PHP: Multiple security vulnerabilities (GLSA 200407-13)
Severity: high
Exploitable: remote
Date: July 15, 2004
Bug(s): #56985
ID: 200407-13
Synopsis
Multiple security vulnerabilities, potentially allowing remote code execution, were found and fixed in PHP.
Background
PHP is a general-purpose scripting language widely used to develop web-based applications. It can run inside a web server using the mod_php module or the CGI version of PHP, or can run stand-alone in a CLI.
Affected Packages
Package: dev-php/php
Vulnerable: <= 4.3.7-r1
Unaffected: >= 4.3.8
Architectures: All supported architectures
Package: dev-php/mod_php
Vulnerable: <= 4.3.7-r1
Unaffected: >= 4.3.8
Architectures: All supported architectures
Package: dev-php/php-cgi
Vulnerable: <= 4.3.7-r1
Unaffected: >= 4.3.8
Architectures: All supported architectures
Description
Several security vulnerabilities were found and fixed in version 4.3.8 of PHP. The strip_tags() function, used to sanitize user input, could in certain cases allow tags containing characters (CAN-2004-0595). When memory_limit is used, PHP might unsafely interrupt other functions (CAN-2004-0594). The ftok and itpc functions were missing safe_mode checks. It was possible to bypass open_basedir restrictions using MySQL's LOAD DATA LOCAL function. Furthermore, the IMAP extension was incorrectly allocating memory and alloca() calls were replaced with emalloc() for better stack protection.
Impact
Successfully exploited, the memory_limit problem could allow remote excution of arbitrary code. By exploiting the strip_tags vulnerability, it is possible to pass HTML code that would be considered as valid tags by the Microsoft Internet Explorer and Safari browsers. Using ftok, itpc or MySQL's LOAD DATA LOCAL, it is possible to bypass PHP configuration restrictions.
Workaround
There is no known workaround that would solve all these problems. All users are encouraged to upgrade to the latest available versions.
Resolution
All PHP, mod_php and php-cgi users should upgrade to the latest stable version: Code: | # emerge sync
# emerge -pv ">=dev-php/php-4.3.8"
# emerge ">=dev-php/php-4.3.8"
# emerge -pv ">=dev-php/mod_php-4.3.8"
# emerge ">=dev-php/mod_php-4.3.8"
# emerge -pv ">=dev-php/php-cgi-4.3.8"
# emerge ">=dev-php/php-cgi-4.3.8" |
References
CAN-2004-0594
CAN-2004-0595
E-Matters Advisory 11/2004
E-Matters Advisory 12/2004
Last edited by GLSA on Sun May 07, 2006 4:51 pm; edited 1 time in total |
|