LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13281: In Xpdf 4.01.01, a heap-based buffer overflow could be triggered in DCTStream::decodeImage() in Stream.cc w...

In Xpdf 4.01.01, a heap-based buffer overflow could be triggered in DCTStream::decodeImage() in Stream.cc when writing to frameBuf memory. It can, for example, be triggered by sending a crafted PDF document to the pdftotext tool. It allows an attacker to use a crafted pdf file to cause Denial of Service, an information leak, or possibly unspecified other impact.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A specially crafted PDF can crash or possibly expose data when processed by Xpdf 4.01.01 tools such as pdftotext. The issue is a memory corruption bug in image decoding. Business risk is highest where automated workflows ingest PDFs from customers, email, or public uploads.

Executive priority

Treat this as a targeted patch and exposure-reduction task, not an emergency based on current evidence. Prioritize internet-facing or customer-facing PDF processing first because crafted files are the described trigger.

Technical view

CVE-2019-13281 is a heap-based buffer overflow in Xpdf 4.01.01, in DCTStream::decodeImage() in Stream.cc while writing frameBuf memory. The CVE record says a crafted PDF can trigger it through pdftotext, causing denial of service, information leak, or possibly other unspecified impact.

Likely exposure

Exposure is most likely on servers, desktops, or batch jobs using Xpdf 4.01.01 or distro packages to parse untrusted PDFs. The supplied metadata lacks complete affected CPEs, downstream package version details, and exact fixed versions.

Exploitation context

The source bundle describes a crafted PDF trigger path but does not cite active exploitation. KEV status is false, so do not treat this as known exploited based on the provided evidence.

Researcher notes

The evidence identifies the vulnerable function and trigger class but omits CVSS, CWE, CPEs, and fixed version details. Validate through version and package provenance rather than assuming all Xpdf deployments are affected.

Mitigation direction

  • Identify any Xpdf or pdftotext use in PDF ingestion workflows.
  • Apply vendor-supported Xpdf or distribution package updates, including relevant Fedora advisories where applicable.
  • Avoid processing untrusted PDFs with affected versions until vendor guidance is applied.
  • Run PDF conversion workloads with least privilege and isolation.
  • Check Xpdf upstream guidance if your platform is not covered by Fedora advisories.

Validation and detection

  • Confirm installed Xpdf and pdftotext versions against vendor package records.
  • Review automated PDF workflows that accept email, upload, or customer-supplied documents.
  • Verify patched packages are deployed on systems processing PDFs.
  • Check recent crash reports involving Xpdf, pdftotext, or PDF conversion jobs.
  • Document whether affected functionality is reachable from untrusted input.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2019-13281 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.