Bug 1470138 - (CVE-2017-2820) CVE-2017-2820 poppler: Integer overflow in the JPEG 2000 image parsing functionality
CVE-2017-2820 poppler: Integer overflow in the JPEG 2000 image parsing functi...
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On:
Blocks: 1470140
  Show dependency treegraph
Reported: 2017-07-12 08:34 EDT by Andrej Nemec
Modified: 2017-08-22 01:50 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-22 01:50:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
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:34:11 EDT
An exploitable integer overflow vulnerability exists in the JPEG 2000 image parsing functionality of freedesktop.org Poppler. A specially crafted PDF file can lead to an integer overflow causing out of bounds memory overwrite on the heap resulting in potential arbitrary code execution. To trigger this vulnerability, a victim must open the malicious PDF in an application using this library.

External References:

Comment 1 Huzaifa S. Sidhpurwala 2017-08-22 01:50:30 EDT
As per upstream advisory:

"Poppler is a popular open source PDF parser library. It is used by default in many open source PDF viewers. The library itself implements a decoder for JPEG 2000 encoded images instead of relying on a more complete implementation (such as OpenJPEG), although it does warn about this at compile time and strongly suggests OpenJPEG be used. By default, this internal implementation will be used by applications. "

However the versions of poppler library shipped with Red Hat Enterprise Linux and Fedora use the system libopenjpeg 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.