Skip to content
Fencer Intel
medium 5.5

CVE-2019-14292 json

An issue was discovered in Xpdf 4.01.01.

published 7y ago modified 4mo ago also EUVD-2019-5519

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

Summary

An issue was discovered in Xpdf 4.01.01. There is an out of bounds read in the function GfxPatchMeshShading::parse at GfxState.cc for typeA!=6 case 1.

Patch / fix

  • poppler SLE Software Development Kit 12 SP5 0.24.4-14.41.1
  • poppler SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 0.43.0-16.40.1
  • poppler-qt SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 0.43.0-16.40.1

suse advisories SUSE-SU-2023:4546-1SUSE-SU-2023:4362-1

Is CVE-2019-14292 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-2019-14292 updated cvss 6.8

xpdf: OOB read in function GfxPatchMeshShading::parse in GfxState.cc

  • Red Hat All currently supported Red Hat products
    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.13% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/TeamSeri0us/pocs/tree/master/xpdf/4.01.01 referenced PoC, tagged "exploit" by a source, unverified
  • forum.xpdfreader.com https://forum.xpdfreader.com/viewtopic.php?f=3&t=41851 referenced PoC, tagged "exploit" by a source, unverified

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.