Skip to content
Fencer Intel
medium 6.5

CVE-2022-34503 json

QPDF v8.4.2 was discovered to contain a heap buffer overflow via the function QPDF::processXRefStream.

published 4y ago modified 4mo ago also EUVD-2022-37458

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

QPDF v8.4.2 was discovered to contain a heap buffer overflow via the function QPDF::processXRefStream. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted PDF file.

Patch / fix

  • qpdf Debian 14, Debian 13, Debian 12 9.0.0-1

debian advisories DEBIAN-CVE-2022-34503

  • qpdf SLES for SAP 15 SP1, SLES for SAP 15, SLES 15-LTSS +9 more 8.0.2-150000.3.5.1
  • qpdf SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES 12 SP5 +6 more 7.1.1-3.8.1

suse advisories SUSE-SU-2022:2670-1SUSE-SU-2022:2669-1

Is CVE-2022-34503 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-34503 updated cvss 4.7

qpdf: a heap buffer overflow via the function QPDF::processXRefStream

  • Red Hat Enterprise Linux 7 qpdf, qpdf-libs Red Hat Enterprise Linux 8 qpdf, qpdf-libs Red Hat Enterprise Linux 9 qpdf, qpdf-libs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/qpdf/qpdf/issues/701 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.