Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1475517 (CVE-2017-11627) - CVE-2017-11627 qpdf: Infinite loop in PointerHolder function in PointerHolder.hh
Summary: CVE-2017-11627 qpdf: Infinite loop in PointerHolder function in PointerHolder.hh
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-11627
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: 1475518 1475519
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-26 20:03 UTC by Pedro Sampaio
Modified: 2019-09-29 14:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-08 03:18:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Pedro Sampaio 2017-07-26 20:03:20 UTC
A stack-consumption vulnerability was found in libqpdf in QPDF 6.0.0,
which allows attackers to cause a denial of service via a crafted file,
related to the PointerHolder function in PointerHolder.hh, aka an
"infinite loop".
Upstream bug:

https://github.com/qpdf/qpdf/issues/118

Upstream patch:

https://github.com/jberkenbilt/qpdf/commit/2f56805a397b4d264bcfdfc248765990084c2933
https://github.com/jberkenbilt/qpdf/commit/97c9344c4b878ddc4723486640688d2d3d38ad32
https://github.com/qpdf/qpdf/commit/ac3c81a8edcb44e2669485630d6718c96a6ad6e9

References:

http://somevulnsofadlab.blogspot.com.br/2017/07/qpdfan-infinite-loop-in-libqpdf_21.html

Comment 1 Pedro Sampaio 2017-07-26 20:03:47 UTC
Created qpdf tracking bugs for this issue:

Affects: epel-6 [bug 1475519]
Affects: fedora-all [bug 1475518]


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