Bug 1786570 (CVE-2019-11047) - CVE-2019-11047 php: information disclosure in exif_read_data()
Summary: CVE-2019-11047 php: information disclosure in exif_read_data()
Status: NEW
Alias: CVE-2019-11047
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1788224 1788225 1786571 1788221 1788222 1788223
Blocks: 1786580
TreeView+ depends on / blocked
Reported: 2019-12-26 09:47 UTC by Dhananjay Arunesh
Modified: 2020-01-08 16:20 UTC (History)
6 users (show)

Fixed In Version: php 7.2Git-2019-12-04
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-12-26 09:47:42 UTC
A vulnerability was found in PHP EXIF extension is parsing EXIF information from an image, e.g. via exif_read_data() function, in PHP versions 7.2.x below 7.2.26, 7.3.x below 7.3.13 and 7.4.0 it is possible to supply it with data what will cause it to read past the allocated buffer. This may lead to information disclosure or crash.


Comment 1 Dhananjay Arunesh 2019-12-26 09:48:59 UTC
Created php tracking bugs for this issue:

Affects: fedora-all [bug 1786571]

Comment 3 Marco Benatto 2020-01-06 18:01:19 UTC
Upstream commit for this bug:

Comment 4 Marco Benatto 2020-01-06 18:14:39 UTC
There's an issue with PHP's EXIF module during a EXIF tag processing. When processing the Maker Note tag exif module fails to validate the data lenght, triggering an out of bounds read on a heap allocated value.
The out of bounds happens when exif_process_IFD_in_MAKERNOTE() function calls strncmp() to compare the Maker Note's id string. An attacker may leverage this by crafting a speciall EXIF section, leading to information disclousure and possible DoS.

This flaw has Low impact regarding Confidentiality as the attack has no control over the information which may be leaked and only a small chunck of heap data will be exposed.

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