This page lists publicly disclosed CVE vulnerabilities affecting glyphandcog xpdfreader (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2021-40226 | xpdfreader 4.03 is vulnerable to Buffer Overflow. | [email protected] | 7.5 | 0.53% | 2022-11-10 | 2025-05-01 |
| CVE-2022-24107 | Xpdf prior to 4.04 lacked an integer overflow check in JPXStream.cc. | [email protected] | 7.8 | 0.08% | 2022-08-30 | 2024-11-21 |
| CVE-2022-24106 | In Xpdf prior to 4.04, the DCT (JPEG) decoder was incorrectly allowing the 'interleaved' flag to be changed after the first scan of the image, leading to an unknown integer-related vulnerability in Stream.cc. | [email protected] | 7.8 | 0.11% | 2022-08-30 | 2024-11-21 |
| CVE-2019-17064 | Catalog.cc in Xpdf 4.02 has a NULL pointer dereference because Catalog.pageLabels is initialized too late in the Catalog constructor. | [email protected] | 5.5 | 0.37% | 2019-10-01 | 2024-11-21 |
| CVE-2019-16115 | In Xpdf 4.01.01, a stack-based buffer under-read could be triggered in IdentityFunction::transform in Function.cc, used by GfxAxialShading::getColor. It can, for example, be triggered by sending a crafted PDF document to the pdftoppm tool. It allows an attacker to use a crafted PDF file to cause Denial of Service or possibly unspecified other impact. | [email protected] | 7.8 | 0.18% | 2019-09-08 | 2024-11-21 |
| CVE-2019-16088 | Xpdf 3.04 has a SIGSEGV in XRef::fetch in XRef.cc after many recursive calls to Catalog::countPageTree in Catalog.cc. | [email protected] | 5.5 | 0.12% | 2019-09-06 | 2024-11-21 |
| CVE-2019-15860 | Xpdf 2.00 allows a SIGSEGV in XRef::constructXRef in XRef.cc. NOTE: 2.00 is a version from November 2002. | [email protected] | 5.5 | 0.17% | 2019-09-03 | 2024-11-21 |
| CVE-2019-14294 | An issue was discovered in Xpdf 4.01.01. There is a use-after-free in the function JPXStream::fillReadBuf at JPXStream.cc, due to an out of bounds read. | [email protected] | 5.5 | 0.19% | 2019-07-27 | 2024-11-21 |
| CVE-2019-14293 | An issue was discovered in Xpdf 4.01.01. There is an out of bounds read in the function GfxPatchMeshShading::parse at GfxState.cc for typeA!=6 case 2. | [email protected] | 5.5 | 0.17% | 2019-07-27 | 2024-11-21 |
| CVE-2019-14292 | An issue was discovered in Xpdf 4.01.01. There is an out of bounds read in the function GfxPatchMeshShading::parse at GfxState.cc for typeA!=6 case 1. | [email protected] | 5.5 | 0.17% | 2019-07-27 | 2024-11-21 |
| CVE-2019-14291 | An issue was discovered in Xpdf 4.01.01. There is an out of bounds read in the function GfxPatchMeshShading::parse at GfxState.cc for typeA==6 case 3. | [email protected] | 5.5 | 0.17% | 2019-07-27 | 2024-11-21 |
| CVE-2019-14290 | An issue was discovered in Xpdf 4.01.01. There is an out of bounds read in the function GfxPatchMeshShading::parse at GfxState.cc for typeA==6 case 2. | [email protected] | 5.5 | 0.17% | 2019-07-27 | 2024-11-21 |
| CVE-2019-14289 | An issue was discovered in Xpdf 4.01.01. There is an integer overflow in the function JBIG2Bitmap::combine at JBIG2Stream.cc for the "multiple bytes per line" case. | [email protected] | 5.5 | 0.17% | 2019-07-27 | 2024-11-21 |
| CVE-2019-14288 | An issue was discovered in Xpdf 4.01.01. There is an Integer overflow in the function JBIG2Bitmap::combine at JBIG2Stream.cc for the "one byte per line" case. | [email protected] | 7.8 | 0.20% | 2019-07-27 | 2024-11-21 |
| CVE-2019-13291 | In Xpdf 4.01.01, there is a heap-based buffer over-read in the function DCTStream::readScan() located at Stream.cc. It can, for example, be triggered by sending a crafted PDF document to the pdftops tool. It might allow an attacker to cause Information Disclosure. | [email protected] | 5.5 | 0.24% | 2019-07-04 | 2024-11-21 |
| CVE-2019-13289 | In Xpdf 4.01.01, there is a use-after-free vulnerability in the function JBIG2Stream::close() located at JBIG2Stream.cc. It can, for example, be triggered by sending a crafted PDF document to the pdftoppm tool. | [email protected] | 7.8 | 0.29% | 2019-07-04 | 2024-11-21 |
| CVE-2019-13288 | In Xpdf 4.01.01, the Parser::getObj() function in Parser.cc may cause infinite recursion via a crafted file. A remote attacker can leverage this for a DoS attack. This is similar to CVE-2018-16646. | [email protected] | 5.5 | 31.54% | 2019-07-04 | 2024-11-21 |
| CVE-2019-13287 | In Xpdf 4.01.01, there is an out-of-bounds read vulnerability in the function SplashXPath::strokeAdjust() located at splash/SplashXPath.cc. It can, for example, be triggered by sending a crafted PDF document to the pdftoppm tool. It might allow an attacker to cause Information Disclosure. This is related to CVE-2018-16368. | [email protected] | 5.5 | 0.20% | 2019-07-04 | 2024-11-21 |
| CVE-2019-13286 | In Xpdf 4.01.01, there is a heap-based buffer over-read in the function JBIG2Stream::readTextRegionSeg() located at JBIG2Stream.cc. It can, for example, be triggered by sending a crafted PDF document to the pdftoppm tool. It might allow an attacker to cause Information Disclosure. | [email protected] | 5.5 | 0.32% | 2019-07-04 | 2024-11-21 |
| CVE-2019-13283 | In Xpdf 4.01.01, a heap-based buffer over-read could be triggered in strncpy from FoFiType1::parse in fofi/FoFiType1.cc because it does not ensure the source string has a valid length before making a fixed-length copy. It can, for example, be triggered by sending a crafted PDF document to the pdftotext tool. It allows an attacker to use a crafted pdf file to cause Denial of Service or an information leak, or possibly have unspecified other impact. | [email protected] | 7.8 | 0.30% | 2019-07-04 | 2024-11-21 |