Qpdf Project
19 vulnerabilities.
All published vulnerabilities with a CVE number in Qpdf Project products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2024-24246 | Qpdf Project Qpdf: Heap Buffer Overflow vulnerability in qpdf 11.9.0 allows attackers to crash the application via the std::__shared_count() function at … | 2024-02-29 | 5.5 |
| CVE-2022-34503 | Qpdf Project Qpdf: QPDF v8.4.2 was discovered to contain a heap buffer overflow via the function QPDF::processXRefStream. This vulnerability allows attackers to cause … | 2022-07-22 | 6.5 |
| CVE-2021-36978 | Qpdf Project Qpdf: QPDF 9.x through 9.1.1 and 10.x through 10.0.4 has a heap-based buffer overflow in Pl_ASCII85Decoder::write (called from Pl_AES_PDF::flush and … | 2021-07-20 | 5.5 |
| CVE-2021-25786 | Qpdf Project Qpdf: An issue was discovered in QPDF version 10.0.4, allows remote attackers to execute arbitrary code via crafted .pdf file to Pl_ASCII85Decoder::write … | 2023-08-11 | 5.3 |
| CVE-2018-18020 | Qpdf Project Qpdf: In QPDF 8.2.1, in libqpdf/QPDFWriter.cc, QPDFWriter::unparseObject and QPDFWriter::unparseChild have recursive calls for a long time, which allows … | 2018-10-06 | 3.3 |
| CVE-2018-9918 | Qpdf Project Qpdf: libqpdf.a in QPDF through 8.0.2 mishandles certain "expected dictionary key but found non-name object" cases, allowing remote attackers to cause a … | 2018-04-10 | 7.8 |
| CVE-2017-18186 | Qpdf Project Qpdf: An issue was discovered in QPDF before 7.0.0. There is an infinite loop due to looping xref tables in QPDF.cc. | 2018-02-13 | 5.5 |
| CVE-2017-18185 | Qpdf Project Qpdf: An issue was discovered in QPDF before 7.0.0. There is a large heap-based out-of-bounds read in the Pl_Buffer::write function in Pl_Buffer.cc. It … | 2018-02-13 | 5.5 |
| CVE-2017-18184 | Qpdf Project Qpdf: An issue was discovered in QPDF before 7.0.0. There is a stack-based out-of-bounds read in the function iterate_rc4 in QPDF_encryption.cc. | 2018-02-13 | 5.5 |
| CVE-2017-18183 | Qpdf Project Qpdf: An issue was discovered in QPDF before 7.0.0. There is an infinite loop in the QPDFWriter::enqueueObject() function in libqpdf/QPDFWriter.cc. | 2018-02-13 | 5.5 |
| CVE-2017-12595 | Qpdf Project Qpdf: The tokenizer in QPDF 6.0.0 and 7.0.b1 is recursive for arrays and dictionaries, which allows remote attackers to cause a denial of service (stack … | 2017-08-27 | 7.8 |
| CVE-2017-11627 | Qpdf Project Qpdf: A stack-consumption vulnerability was found in libqpdf in QPDF 6.0.0, which allows attackers to cause a denial of service via a crafted file, … | 2017-07-25 | 5.5 |
| CVE-2017-11626 | Qpdf Project Qpdf: A stack-consumption vulnerability was found in libqpdf in QPDF 6.0.0, which allows attackers to cause a denial of service via a crafted file, … | 2017-07-25 | 5.5 |
| CVE-2017-11625 | Qpdf Project Qpdf: A stack-consumption vulnerability was found in libqpdf in QPDF 6.0.0, which allows attackers to cause a denial of service via a crafted file, … | 2017-07-25 | 5.5 |
| CVE-2017-11624 | Qpdf Project Qpdf: A stack-consumption vulnerability was found in libqpdf in QPDF 6.0.0, which allows attackers to cause a denial of service via a crafted file, … | 2017-07-25 | 5.5 |
| CVE-2017-9210 | Qpdf Project Qpdf: libqpdf.a in QPDF 6.0.0 allows remote attackers to cause a denial of service (infinite recursion and stack consumption) via a crafted PDF document, … | 2017-05-23 | 5.5 |
| CVE-2017-9209 | Qpdf Project Qpdf: libqpdf.a in QPDF 6.0.0 allows remote attackers to cause a denial of service (infinite recursion and stack consumption) via a crafted PDF document, … | 2017-05-23 | 5.5 |
| CVE-2017-9208 | Qpdf Project Qpdf: libqpdf.a in QPDF 6.0.0 allows remote attackers to cause a denial of service (infinite recursion and stack consumption) via a crafted PDF document, … | 2017-05-23 | 5.5 |
| CVE-2015-9252 | Qpdf Project Qpdf: An issue was discovered in QPDF before 7.0.0. Endless recursion causes stack exhaustion in QPDFTokenizer::resolveLiteral() in QPDFTokenizer.cc, … | 2018-02-13 | 5.5 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.