PatchTheCVElibextractor vulnerabilities
Recent CVEs affecting libextractor products. 5 tracked.
libextractor has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-05-18. Highest priority: CVE-2005-3625 (score 63/100).
- CVE-2006-2458 MEDIUM 4.0 DOWNGRADE Multiple heap-based buffer overflows in Libextractor 0.5.13 and earlier allow remote attackers to execute arbi
- 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-3626 MEDIUM 5.0 DOWNGRADE DOWNGRADE Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allow
- CVE-2005-3625 HIGH 10.0 DOWNGRADE DOWNGRADE Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allow
- CVE-2005-3624 MEDIUM 5.0 DOWNGRADE DOWNGRADE The CCITTFaxStream::CCITTFaxStream function in Stream.cc for xpdf, gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS
FAQ
How do I fix libextractor 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 libextractor being exploited right now?
None of the tracked libextractor CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libextractor CVE should I patch first?
CVE-2005-3625 currently ranks highest (63/100): Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allow.