Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1416499 - (CVE-2016-7480) CVE-2016-7480 php: Use of uninitialized value in SplObjectStorag::unserialize
CVE-2016-7480 php: Use of uninitialized value in SplObjectStorag::unserialize
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161006,repor...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-25 11:05 EST by Adam Mariš
Modified: 2017-01-26 05:33 EST (History)
9 users (show)

See Also:
Fixed In Version: php 7.0.12
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-25 11:10:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2017-01-25 11:05:54 EST
The SplObjectStorage unserialize implementation in ext/spl/spl_observer.c in PHP before 7.0.12 does not verify that a key is an object, which allows remote attackers to execute arbitrary code or cause a denial of service (uninitialized memory access) via crafted serialized data.

Upstream bug:

https://bugs.php.net/bug.php?id=73257

Upstream patch:

https://github.com/php/php-src/commit/61cdd1255d5b9c8453be71aacbbf682796ac77d4

External References:

http://blog.checkpoint.com/2016/12/27/check-point-discovers-three-zero-day-vulnerabilities-web-programming-language-php-7/
Comment 1 Adam Mariš 2017-01-25 11:10:35 EST
This issue happens when untrusted input is being unserialized which is documented as being insecure. Unserialization can result in code being loaded and executed due to object instantiation and autoloading, and a malicious user may be able to exploit this. Consider using safe, standard data interchange  format such as JSON.

Note You need to log in before you can comment on or make changes to this bug.