|Description||The Adobe PDF specification 1.3, as implemented by (a) xpdf 3.0.1 patch 2, (b) kpdf in KDE before 3.5.5, (c) poppler before 0.5.4, and other products, allows remote attackers to have an unknown impact, possibly including denial of service (infinite loop), arbitrary code execution, or memory corruption, via a PDF file with a (1) crafted catalog dictionary or (2) a crafted Pages attribute that references an invalid page tree node.|
|Source||CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)|
Vulnerable and fixed packages
The table below lists information on source packages.
|bullseye (security), bullseye||20.09.0-3.1+deb11u1||fixed|
|sid, trixie, bookworm||22.12.0-2||fixed|
|sid, trixie, bookworm||3.04+git20220601-1||fixed|
The information below is based on the following data on fixed versions.
|Package||Type||Release||Fixed Version||Urgency||Origin||Debian Bugs|
- swftools <not-affected> (first version that entered the archive is based on xpdf 3.02)
hardly a security issue; if someone sends someone a crafted PDF file triggering
such an endless loop the user will simply abort kpdf and never look at
that file again, this is only denial of service by a _very_ far stretch
of imagination. I suppose KDE Security only issued an update for it
because the shared underlying code was part of the Month of Apple Bugs
and they wanted to debunk claims of code injection.