Jump to content

Advisories MDKSA-2006:122: Updated php packages fix multiple vulnerabilities


paul
 Share

Recommended Posts

Multiple buffer overflows in the gd graphics library (libgd) 2.0.21 and

earlier may allow remote attackers to execute arbitrary code via

malformed image files that trigger the overflows due to improper calls

to the gdMalloc function. One instance in gd_io_dp.c does not appear to

be corrected in the embedded copy of GD used in php to build the php-gd

package. (CVE-2004-0941)

 

Integer overflows were reported in the GD Graphics Library (libgd)

2.0.28, and possibly other versions. These overflows allow remote

attackers to cause a denial of service and possibly execute arbitrary

code via PNG image files with large image rows values that lead to a

heap-based buffer overflow in the gdImageCreateFromPngCtx() function.

PHP, as packaged in Mandriva Linux, contains an embedded copy of the

GD library, used to build the php-gd package. (CVE-2004-0990)

 

The c-client library 2000, 2001, or 2004 for PHP 3.x, 4.x, and 5.x,

when used in applications that accept user-controlled input for the

mailbox argument to the imap_open function, allow remote attackers to

obtain access to an IMAP stream data structure and conduct unauthorized

IMAP actions. (CVE-2006-1017)

 

Integer overflow in the wordwrap function in string.c in might allow

context-dependent attackers to execute arbitrary code via certain long

arguments that cause a small buffer to be allocated, which triggers a

heap-based buffer overflow in a memcpy function call, a different

vulnerability than CVE-2002-1396. (CVE-2006-1990) The previous update

for this issue did not resolve the issue on 64bit platforms.

 

The cURL library (libcurl) in PHP 4.4.2 and 5.1.4 allows attackers to

bypass safe mode and read files via a file:// request containing nul

characters. (CVE-2006-2563)

 

Buffer consumption vulnerability in the tempnam function in PHP 5.1.4

and 4.x before 4.4.3 allows local users to bypass restrictions and

create PHP files with fixed names in other directories via a pathname

argument longer than MAXPATHLEN, which prevents a unique string from

being appended to the filename. (CVE-2006-2660)

 

The LZW decoding in the gdImageCreateFromGifPtr function in the Thomas

Boutell graphics draw (GD) library (aka libgd) 2.0.33 allows remote

attackers to cause a denial of service (CPU consumption) via malformed

GIF data that causes an infinite loop. PHP, as packaged in Mandriva

Linux, contains an embedded copy of the GD library, used to build the

php-gd package. (CVE-2006-2906)

 

The error_log function in PHP allows local users to bypass safe mode

and open_basedir restrictions via a "php://" or other scheme in the

third argument, which disables safe mode. (CVE-2006-3011)

 

An unspecified vulnerability in session.c in PHP before 5.1.3 has

unknown impact and attack vectors, related to "certain characters in

session names", including special characters that are frequently

associated with CRLF injection, SQL injection, and cross-site scripting

(XSS) vulnerabilities. NOTE: while the nature of the vulnerability is

unspecified, it is likely that this is related to a violation of an

expectation by PHP applications that the session name is alphanumeric,

as implied in the PHP manual for session_name(). (CVE-2006-3016)

 

An unspecified vulnerability in PHP before 5.1.3 can prevent a variable

from being unset even when the unset function is called, which might

cause the variable's value to be used in security-relevant operations.

(CVE-2006-3017)

 

An unspecified vulnerability in the session extension functionality in

PHP before 5.1.3 has unkown impact and attack vectors related to heap

corruption. (CVE-2006-3018)

 

The GD related issues (CVE-2004-0941, CVE-2004-0990, CVE-2006-2906)

affect only Corporate 3 and Mandrake Network Firewall 2.

 

The php-curl issue (CVE-2006-2563) affects only Mandriva 2006.0.

 

Updated packages have been patched to address all these issues. Once

these packages have been installed, you will need to restart Apache

(service httpd restart) in order for the changes to take effect.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...