Bug 1707299 (CVE-2019-11036) - CVE-2019-11036 php: Buffer over-read in exif_process_IFD_TAG() leading to information disclosure
Summary: CVE-2019-11036 php: Buffer over-read in exif_process_IFD_TAG() leading to inf...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-11036
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1710410 1707300 1710408 1710411 1710412 1710413
Blocks: 1707301
TreeView+ depends on / blocked
 
Reported: 2019-05-07 08:47 UTC by Marian Rehak
Modified: 2019-11-14 11:47 UTC (History)
6 users (show)

Fixed In Version: php 7.1.29, php 7.2.18, php 7.3.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 08:48:04 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3727 None None None 2019-11-06 10:12:45 UTC
Red Hat Product Errata RHSA-2019:2519 None None None 2019-08-19 08:43:00 UTC
Red Hat Product Errata RHSA-2019:3299 None None None 2019-11-01 13:01:01 UTC

Description Marian Rehak 2019-05-07 08:47:28 UTC
When processing certain files, PHP EXIF extension in versions 7.1.x below 7.1.29, 7.2.x below 7.2.18 and 7.3.x below 7.3.5 can be caused to read past allocated buffer in exif_process_IFD_TAG function. This may lead to information disclosure or crash.

External Reference:
https://bugs.php.net/bug.php?id=77950

Upstream commit:
http://git.php.net/?p=php-src.git;a=commit;h=f80ad18afae2230c2c1802c7d829100af646874e

Comment 1 Marian Rehak 2019-05-07 08:47:38 UTC
Created php tracking bugs for this issue:

Affects: fedora-all [bug 1707300]

Comment 6 Marco Benatto 2019-05-15 14:36:53 UTC
Statement:

This issue affects the versions of php as shipped with Red Hat Enterprise Linux 5, 6, 7 and 8 as well php53 as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having a security impact of Low. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. 

Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a
security impact of Low, and is not currently planned to be addressed in future updates. For additional information, refer to the
Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.

Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.

This issue did affect the versions of rh-php70-php, rh-php71-php and rh-php72-php as shipped with Red Hat Software Collections.

Comment 7 errata-xmlrpc 2019-08-19 08:42:59 UTC
This issue has been addressed in the following products:

  Red Hat Software Collections for Red Hat Enterprise Linux 7
  Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS

Via RHSA-2019:2519 https://access.redhat.com/errata/RHSA-2019:2519

Comment 8 Product Security DevOps Team 2019-08-19 08:48:04 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2019-11036

Comment 9 errata-xmlrpc 2019-11-01 13:01:00 UTC
This issue has been addressed in the following products:

  Red Hat Software Collections for Red Hat Enterprise Linux 7
  Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS

Via RHSA-2019:3299 https://access.redhat.com/errata/RHSA-2019:3299


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