Vulnerabilities > Glyphandcog > Xpdfreader
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2019-07-27 | CVE-2019-14291 | Out-of-bounds Read vulnerability in Glyphandcog Xpdfreader 4.01.01 An issue was discovered in Xpdf 4.01.01. | 4.3 |
| 2019-07-27 | CVE-2019-14290 | Out-of-bounds Read vulnerability in Glyphandcog Xpdfreader 4.01.01 An issue was discovered in Xpdf 4.01.01. | 4.3 |
| 2019-07-27 | CVE-2019-14289 | Integer Overflow or Wraparound vulnerability in Glyphandcog Xpdfreader 4.01.01 An issue was discovered in Xpdf 4.01.01. | 4.3 |
| 2019-07-27 | CVE-2019-14288 | Integer Overflow or Wraparound vulnerability in Glyphandcog Xpdfreader 4.01.01 An issue was discovered in Xpdf 4.01.01. | 4.3 |
| 2019-07-04 | CVE-2019-13291 | Out-of-bounds Read vulnerability in Glyphandcog Xpdfreader 4.01.01 In Xpdf 4.01.01, there is a heap-based buffer over-read in the function DCTStream::readScan() located at Stream.cc. | 4.3 |
| 2019-07-04 | CVE-2019-13289 | Use After Free vulnerability in Glyphandcog Xpdfreader 4.01.01 In Xpdf 4.01.01, there is a use-after-free vulnerability in the function JBIG2Stream::close() located at JBIG2Stream.cc. | 6.8 |
| 2019-07-04 | CVE-2019-13288 | Uncontrolled Recursion vulnerability in Glyphandcog Xpdfreader 4.01.01 In Xpdf 4.01.01, the Parser::getObj() function in Parser.cc may cause infinite recursion via a crafted file. | 4.3 |
| 2019-07-04 | CVE-2019-13287 | Out-of-bounds Read vulnerability in Glyphandcog Xpdfreader 4.01.01 In Xpdf 4.01.01, there is an out-of-bounds read vulnerability in the function SplashXPath::strokeAdjust() located at splash/SplashXPath.cc. | 4.3 |
| 2019-07-04 | CVE-2019-13286 | Out-of-bounds Read vulnerability in multiple products In Xpdf 4.01.01, there is a heap-based buffer over-read in the function JBIG2Stream::readTextRegionSeg() located at JBIG2Stream.cc. | 5.5 |
| 2019-07-04 | CVE-2019-13283 | Out-of-bounds Read vulnerability in multiple products 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. | 7.8 |