Skip to content
Fencer Intel
high 7.5

CVE-2017-2818 json

An exploitable heap overflow vulnerability exists in the image rendering functionality of Poppler 0.53.0.

published 2017-07-12 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11959

cvss
7.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

An exploitable heap overflow vulnerability exists in the image rendering functionality of Poppler 0.53.0. A specifically crafted PDF can cause an overly large number of color components during image rendering, resulting in heap corruption. An attacker controlled PDF file can be used to trigger this vulnerability.

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-2818 updated cvss 7.0

poppler: Heap-buffer overflow in the image rendering functionality

  • Red Hat Enterprise Linux 5 poppler Red Hat Enterprise Linux 6 poppler, poppler-qt, poppler-qt4, poppler-glib, poppler-utils Red Hat Enterprise Linux 7 poppler, poppler-qt, poppler-cpp, poppler-glib, poppler-demos, poppler-utils
    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

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

CVSS scores

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

Affected products

  • Poppler Poppler

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.