After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 625849 - crash on opening corrupt pdf
crash on opening corrupt pdf
Status: RESOLVED NOTGNOME
Product: evince
Classification: Core
Component: general
2.30.x
Other Linux
: Normal critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-02 16:16 UTC by hamfbohne
Modified: 2010-08-03 07:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Corrupt PDF from http://www.jailbreakme.com/_/ which causes evince to crash. (12.86 KB, application/pdf)
2010-08-02 16:16 UTC, hamfbohne
Details

Description hamfbohne 2010-08-02 16:16:39 UTC
Created attachment 166995 [details]
Corrupt PDF from http://www.jailbreakme.com/_/ which causes evince to crash.

I just read there is a bug in the apple iOS pdf reader which can be used to jailbreak an iPhone [1]. If you open these corrupt files with evince, it crashes leaving the following message:

$ evince iPod3,1_3.1.3.pdf 
Error: PDF file is damaged - attempting to reconstruct xref table...
Error: Bad color space 'Cs1'
Error (94): Bad color space (fill)
Error (103): Incorrect number of arguments in 'sc' command
Segmentation fault

This happens with probably all (didn't try them all to be honest) files at http://www.jailbreakme.com/_/

Just in case the website is down (due to heavy traffic or whatever) I attached one of the pdfs.

I did a quick search if the bug has already been reported but I can't decide if any of the "crashes on opening pdf-file" is related to this bug. Sorry if its a duplicate.

[1]http://www.h-online.com/security/news/item/iPhone-jailbroken-by-Safari-vulnerability-again-Update-1049234.html
Comment 1 Carlos Garcia Campos 2010-08-03 07:39:09 UTC
This is a crash in poppler, I've just forwarded it to the freedesktop.org bugzilla:

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

Thanks for reporting