Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 19 Jan 2012 22:00:35 -0700
From: Kurt Seifried <kseifried@...hat.com>
To: security@....net, oss-security@...ts.openwall.com
Subject: Potential security issues fixed in PHP 5.3.9

Hi, in addition to the xslt arbitrary file creation) there are some more potential security vulnerabilities that appear to have been fixed in 5.3.9. Can you confirm if these are not security issues? Also will you need CVE assignments for the ones that are (I can help with that).

Sending to security@....net again and cc'ing oss-sec in case anyone on the list has ideas/comments.

>From the ChangeLog:

===========================================================
Fixed bug #60150 (Integer overflow during the parsing of invalid exif
header). (Stas, flolechaud at gmail dot com) - security bug
There is an integer overflow in ext/exif/exif.c that can be used in order to
cause a denial of service or read arbitrary memory.

==========
Fixed bug #55776 (PDORow to session bug). (Johannes)
Is a Apache crash. It gives a CGI/FastCGI Send/Don't Send window.
http://img171.imageshack.us/img171/3953/57126366.jpg [Open URL]
After few minutes is crashing apache server:
http://img840.imageshack.us/img840/2981/21231006.jpg [Open URL] 

==========
Fixed bug #60279 (Fixed NULL pointer dereference in
stream_socket_enable_crypto, case when ssl_handle of session_stream is
not initia\
lized.) (shm) - (needs bad code)

==========
Fixed bug #55622 (memory corruption in parse_ini_string). (Pierre) -
need access to ini style config, but can cause memory corruption\
 (code exec?)

==========
Fixed bug #53502 (strtotime with timezone memory leak). (Derick) - minor
dos?

-- -- Kurt Seifried / Red Hat Security Response Team


Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.