Bug 33722 - poppler fails to extract OpenAction
Summary: poppler fails to extract OpenAction
Status: RESOLVED INVALID
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium major
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-30 08:55 UTC by Ilya Gorenbein
Modified: 2011-02-06 03:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
NOTE!!! Test file is MALICIOUS! (32.20 KB, application/octet-stream)
2011-01-30 09:09 UTC, Ilya Gorenbein
Details

Description Ilya Gorenbein 2011-01-30 08:55:36 UTC
Hello,

I am using poppler version 0.16.0. 

Below is a part of code I am trying to run.

// --------------------------------------

PDFDoc pdf_doc_obj;

XRef* xref = pdf_doc_obj.getXRef();

Object xref_catalog;
xref -> getCatalog( &xref_catalog );

Dict* catalog_dictionary = xref_catalog.getDict();
catalog_dictionary -> lookup( "OpenAction", &obj );

// --------------------------------------

poppler fails to find "OpenAction" object. 
I tried the same on version 0.12.4. It was found OK.


Please advise.
Thanks



Test file is attached. 

NOTE!!! The attached test file is MALICIOUS!!!

Attached file is a password protected archive.
Comment 1 Ilya Gorenbein 2011-01-30 09:09:32 UTC
Created attachment 42721 [details]
NOTE!!! Test file is MALICIOUS!

The files was archived with 7z.
Comment 2 Albert Astals Cid 2011-02-05 07:05:12 UTC
Not a bug, the XRef points for the object 5 to be at offset 316 and when we go there, we don't find object 5 but object 6 thus we don't return anything.
Comment 3 Ilya Gorenbein 2011-02-05 23:32:17 UTC
Poppler version 0.12.4 is able to extract the object. Is there a bug in v. 0.12.4?
Comment 4 Albert Astals Cid 2011-02-06 03:57:24 UTC
Don't know, maybe it was less scrict with that things, but given that this is a file broken on purpose doesn't worry me at all.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.