Quoting upcoming oCERT advisory:
The poppler PDF rendering library suffers a memory management bug which leads
to arbitrary code execution.
The vulnerability is present in the Page class constructor/destructor. The
pageWidgets object is not initialized in the Page constructor if specific
conditions are met, but it is deleted afterwards in the destructor regardless
of its initialization.
oCERT advisory credits: Felipe Andres Manzano
Created attachment 311147 [details]
Public now via:
This issue did not affect version of poppler as shipped in Red Hat Enterprise
Linux 5, or other PDF parsing applications derived from xpdf as shipped in Red
Hat Enterprise Linux 2.1, 3, 4, and 5.
Detailed description and public PoC by Felipe Andres Manzano:
poppler-0.6.2-2.fc8 has been submitted as an update for Fedora 8
poppler-0.8.1-2.fc9 has been submitted as an update for Fedora 9
poppler-0.8.1-2.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update poppler'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-7012
poppler-0.6.2-2.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
To further extend comment #5:
As detailed in Felipes advisory , this issue occurs when pageWidgets with uninitialized value is freed in Page::~Page() destructor. pageWidgets was only introduced in poppler in (or around) upstream version 0.6. The code does not exist in the xpdf, on which poppler is based.
poppler-0.8.1-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
This issue was addressed in: