CVE-2005-3627: n/a vulnerability

CVE-2005-3627: Stream.cc in Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, a...

Stream.cc in Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allows attackers to modify memory and possibly execute arbitrary code via a DCTDecode stream with (1) a large "number of components" value that is not checked by DCTStream::readBaselineSOF or DCTStream::readProgressiveSOF, (2) a large "Huffman table index" value that is not checked by DCTStream::readHuffmanTables, and (3) certain uses of the scanInfo.numComps value by DCTStream::readScanInfo.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 23:17 UTC (UTC+00:00)

Security readout for executives and security teams

This is a PDF-processing memory corruption issue in Xpdf-derived code. A crafted PDF using DCTDecode image data may corrupt memory and possibly run code inside the viewer, converter, printer, or indexing service that processes it. The sources do not provide CVSS or current exploitation evidence. Exposure is most likely on legacy systems that still use vulnerable Xpdf-derived PDF parsing libraries or bundled tools. Risk is higher where untrusted PDFs are opened, converted, indexed, printed, or processed automatically by server-side workflows. Prioritize remediation where PDF processing is exposed to customers, email attachments, uploads, or print workflows. The issue is old, but legacy dependencies can keep it alive in embedded tools and unattended services. Mitigation focus: Apply relevant vendor security updates for affected Xpdf-derived packages.; Prioritize systems processing untrusted PDFs automatically or at scale.; Check vendor advisories before assuming a package or fork is fixed..

Prepared: Jun 29, 2026, 15:49 UTC (UTC+00:00)

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2005-3627 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: Jan 6, 2006, 22:00 UTC (UTC+00:00)

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

2Source links

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
USN-236-1CVE reference · vendor-advisory, x_refsource_UBUNTU

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.