Skip to content
Fencer Intel
medium 5.5

CVE-2017-18184 json

An issue was discovered in QPDF before 7.0.0.

published 2018-02-13 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-9319

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

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.

Patch / fix

  • qpdf_project qpdf 7.0.0
  • qpdf Debian 14, Debian 13, Debian 12 7.0.0-1

debian advisories DEBIAN-CVE-2017-18184

  • qpdf Ubuntu 14.04 LTS 8.0.2-3~14.04.1
  • qpdf Ubuntu 16.04 LTS 8.0.2-3~16.04.1

ubuntu advisories UBUNTU-CVE-2017-18184

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • qpdf Arch Linux 7.0.0-1

arch linux advisories AVG-620

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-2017-18184 updated cvss 3.3

qpdf: out-of-bounds read in iterate_rc4 in QPDF_encryption.cc

  • Red Hat Enterprise Linux 7 qpdf, qpdf-libs
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 8 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.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

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.