Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 163920 - CAN-2005-2097 gpdf DoS
CAN-2005-2097 gpdf DoS
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gpdf (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kristian Høgsberg
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-07-21 19:34 EDT by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
4 users (show)

See Also:
Fixed In Version: RHSA-2005-708
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-10 13:38:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:708 normal SHIPPED_LIVE Moderate: gpdf security update 2005-08-10 00:00:00 EDT

  None (edit)
Description Josh Bressers 2005-07-21 19:34:44 EDT
+++ This bug was initially created as a clone of Bug #163918 +++

A broken PDF file is will create a file in /tmp and continue to fill it until
the filesystem is full.
Comment 1 Josh Bressers 2005-07-21 19:35:50 EDT
The patch for this issue is attachment 117043 [details]
The demo exploit for this issue is attachment 117042 [details]
Comment 2 Josh Bressers 2005-07-21 19:36:46 EDT
gpdf contains an internal version of xpdf.
Comment 5 Kristian Høgsberg 2005-08-01 16:51:48 EDT
Errata filed:

Comment 6 Mark J. Cox 2005-08-10 04:38:32 EDT
removing embargo
Comment 7 Red Hat Bugzilla 2005-08-10 13:38:40 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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