CVE-2019-14288 json
An issue was discovered in Xpdf 4.01.01.
published 7y ago modified 4mo ago also EUVD-2019-5515
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
An issue was discovered in Xpdf 4.01.01. There is an Integer overflow in the function JBIG2Bitmap::combine at JBIG2Stream.cc for the "one byte per line" case.
Is CVE-2019-14288 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 FencerVendor 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-14288 updated cvss 6.2
xpdf: integer overflow in function JBIG2Bitmap::combine in JBIG2Stream.cc
-
Red Hat All currently supported Red Hat productsnot 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.04% chance of exploitation in the next 30 days, higher than 64% 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 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
-
github.com
/TeamSeri0us/pocs/tree/master/xpdf/4.01.01
exploit, third-party-advisory
-
forum.xpdfreader.com
/viewtopic.php?f=3&t=41851
exploit, third-party-advisory
Sources
- CVE List CVE-2019-14288
- NVD CVE-2019-14288
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.