Security readout for executives and security teams
Plain-English summary
CVE-2019-14294 is a memory-safety issue in Xpdf 4.01.01. A crafted PDF could trigger a use-after-free in JPXStream processing. The supplied sources do not provide CVSS, confirmed impact, affected packaging details, or a vendor fix, so urgency depends on where Xpdf handles untrusted PDFs.
Executive priority
Treat this as a targeted remediation item if Xpdf processes untrusted PDFs. It is not KEV-listed in the supplied data, but public PoC availability raises operational concern.
Technical view
The CVE describes a use-after-free in JPXStream::fillReadBuf in JPXStream.cc, associated with an out-of-bounds read. The known product evidence is Xpdf 4.01.01. Public references include a PoC repository and an Xpdf forum thread, but the bundle does not confirm active exploitation or remediation details.
Likely exposure
Exposure is most likely where Xpdf 4.01.01, or software bundling it, parses PDFs from email, uploads, document workflows, archives, or other untrusted sources.
Exploitation context
A public PoC reference is listed, but the source bundle says KEV is false and provides no cited evidence of active exploitation in the wild.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, patch version, or impact statement is included. Keep findings constrained to Xpdf 4.01.01 unless internal evidence shows bundled or downstream exposure.
Mitigation direction
- Inventory systems and applications using Xpdf 4.01.01.
- Check Xpdf vendor guidance for fixed versions or patches.
- Avoid processing untrusted PDFs with affected Xpdf builds.
- Run PDF parsing in sandboxed, least-privilege environments.
- Prioritize replacement where Xpdf is internet-facing or automated.
Validation and detection
- Confirm Xpdf versions through package inventory or SBOM data.
- Identify workflows that parse PDFs from external users.
- Review crash reports for JPXStream or PDF parsing failures.
- Check the CVE record and Xpdf forum for remediation updates.
- Document compensating controls around PDF ingestion paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-14294 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/TeamSeri0us/pocs/tree/master/xpdf/4.01.01CVE reference · x_refsource_MISC
- https://forum.xpdfreader.com/viewtopic.php?f=3&t=41851CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.