Bug 163924 - gpdf DoS
Summary: gpdf DoS
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gpdf
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Marco Pesenti Gritti
QA Contact:
URL:
Whiteboard: impact=moderate,source=vendorsec,repo...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-22 00:35 UTC by Josh Bressers
Modified: 2008-02-12 01:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-12 01:25:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Josh Bressers 2005-07-22 00:35:53 UTC
+++ 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.

The patch for this issue is attachment 117043 [details]
The demo exploit for this issue is attachment 117042 [details]

Comment 1 Josh Bressers 2005-07-22 00:36:52 UTC
This issue also affects FC3

Comment 2 Josh Bressers 2005-07-22 00:37:41 UTC
err, this issue only affects FC3

Comment 3 Marco Pesenti Gritti 2005-07-25 08:03:17 UTC
For FC4 I think this apply to poppler instead.

Comment 4 Josh Bressers 2005-07-25 11:10:21 UTC
Marco,

I'm not sure if this issue affects poppler.  I can't get evince to fill up /tmp
when I open this PDF file (I know it's the same code, but for some reason it's
not crashing).

Comment 5 Mark J. Cox 2005-08-10 08:39:27 UTC
Removing embargo

Comment 6 Matthew Miller 2006-07-10 20:31:04 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 7 petrosyan 2008-02-12 01:25:56 UTC
Fedora Core 3 is not maintained anymore.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.


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