gpdf vulnerabilities and fixes
Recent CVEs affecting gpdf, with upgrade or downgrade steps. 6 tracked.
gpdf has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2009-12-21. Highest priority: CVE-2004-0888 (score 59/100).
- CVE-2009-4035 HIGH 9.3 DOWNGRADE DOWNGRADE The FoFiType1::parse function in fofi/FoFiType1.cc in Xpdf 3.0.0, gpdf 2.8.2, kpdf in kdegraphics 3.3.1, and p
- CVE-2007-3387 MEDIUM 6.8 UPGRADE UPGRADE Integer overflow in the StreamPredictor::StreamPredictor function in xpdf 3.02, as used in (1) poppler before
- CVE-2006-1244 HIGH 7.6 DOWNGRADE DOWNGRADE Unspecified vulnerability in certain versions of xpdf after 3.00, as used in various products including (a) pd
- CVE-2005-0206 HIGH 7.5 DOWNGRADE DOWNGRADE The patch for integer overflow vulnerabilities in Xpdf 2.0 and 3.0 (CVE-2004-0888) is incomplete for 64-bit ar
- CVE-2004-0889 HIGH 10.0 DOWNGRADE DOWNGRADE Multiple integer overflows in xpdf 3.0, and other packages that use xpdf code such as CUPS, allow remote attac
- CVE-2004-0888 HIGH 10.0 DOWNGRADE DOWNGRADE Multiple integer overflows in xpdf 2.0 and 3.0, and other packages that use xpdf code such as CUPS, gpdf, and
FAQ
How do I fix gpdf vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is gpdf being exploited right now?
None of the tracked gpdf CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which gpdf CVE should I patch first?
CVE-2004-0888 currently ranks highest (59/100): Multiple integer overflows in xpdf 2.0 and 3.0, and other packages that use xpdf code such as CUPS, gpdf, and .