Bug 1470139 - (CVE-2017-2818) CVE-2017-2818 poppler: Heap-buffer overflow in the image rendering functionality
CVE-2017-2818 poppler: Heap-buffer overflow in the image rendering functionality
Status: CLOSED NOTABUG
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=20170707,repor...
: Security
Depends On:
Blocks: 1470140
  Show dependency treegraph
 
Reported: 2017-07-12 08:35 EDT by Andrej Nemec
Modified: 2017-08-22 01:52 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-22 01:52:36 EDT
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 Andrej Nemec 2017-07-12 08:35:28 EDT
An exploitable heap overflow vulnerability exists in the image rendering functionality of Poppler. A specifically crafted PDF can cause an overly large number of color components during image rendering, resulting in heap corruption. An attacker controlled PDF file can be used to trigger this vulnerability.

External References:

https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0319
Comment 1 Huzaifa S. Sidhpurwala 2017-08-22 01:52:36 EDT
As per the upstream advisory:

"The Poppler library, by default, uses a private implementation of reading and rendering images. There is a compilation option for libjpeg support, but the flag is not enabled by default. This private implementation contains assumptions about the JPEG file headers that can lead to heap corruption when broken."

However the version of poppler library shipped with Red Hat Enterprise Linux and Fedora use the system libjpeg library, therefore they are not affected by this flaw.

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