Bug 1466442 (CVE-2017-9775) - CVE-2017-9775 poppler: Stack-buffer overflow in GfxState.cc
Summary: CVE-2017-9775 poppler: Stack-buffer overflow in GfxState.cc
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2017-9775
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1459067 1459068 1483504 1483505
Blocks: 1479824
TreeView+ depends on / blocked
 
Reported: 2017-06-29 15:34 UTC by Andrej Nemec
Modified: 2019-09-29 14:15 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A stack-based buffer overflow was found in the poppler library. An attacker could create a malicious PDF file that would cause applications that use poppler (such as Evince) to crash, or potentially execute arbitrary code when opened.
Clone Of:
Environment:
Last Closed: 2017-08-31 14:05:13 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2551 0 normal SHIPPED_LIVE Moderate: poppler security update 2017-08-30 18:00:52 UTC

Description Andrej Nemec 2017-06-29 15:34:35 UTC
Poppler has a stack-based buffer overflow in GfxState.cc, which allows attackers to cause a denial of service (application crash) via a crafted PDF document.

Upstream issue:

https://bugs.freedesktop.org/show_bug.cgi?id=101540

Upstream patch:

https://cgit.freedesktop.org/poppler/poppler/commit/?id=8f4ff8243a3d599ff2a6c08b1da389e606ba4fc9

Comment 1 Andrej Nemec 2017-06-29 15:39:04 UTC
Created mingw-poppler tracking bugs for this issue:

Affects: fedora-all [bug 1459068]


Created poppler tracking bugs for this issue:

Affects: fedora-all [bug 1459067]

Comment 9 errata-xmlrpc 2017-08-30 14:08:55 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2017:2551 https://access.redhat.com/errata/RHSA-2017:2551


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