Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 30 Mar 2015 23:42:01 +0200
From: Tomas Hoger <>
Subject: Re: CVE Request: PHP SoapClient's __call() type
 confusion through unserialize()

On Fri, 20 Mar 2015 20:35:59 +0100 Andrea Palazzo wrote:

> I'd like to request a CVE for the PHP Sec Bug #69085.
> Description:
> SoapClient's __call() method is prone to a type confusion
> vulnerability which can be used to gain remote code execution through
> unsafe unserialize() calls.
> Info:

There is another unserialize issue fixed in 5.6.7, 5.5.23 and 5.4.39
and currently listed on PHP 5 Changelog page:

Fixed bug #68976 (Use After Free Vulnerability in unserialize()). (CVE-2015-0231)

While this lists CVE, it's CVE that was assigned to an issue fixed in
5.6.5, 5.5.21 and 5.4.37:

Fixed bug #68710 (Use After Free Vulnerability in PHP's unserialize()). (CVE-2015-0231)

New id seems to be required for the new issue.

Tomas Hoger / Red Hat Product Security

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.