CVE-2005-3625
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedXpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allows attackers to cause a denial of service (infinite loop) via streams that end prematurely, as demonstrated using the (1) CCITTFaxDecode and (2) DCTDecode streams, aka "Infinite CPU spins."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA legacy NVD category grouping weaknesses in how resources — memory, file handles, connections — are allocated, used, and released. It gathers leaks, exhaustion, and lifecycle bugs under one label rather than naming a single flaw. The fix depends on the specific resource issue, generally pairing acquisition with release and bounding what any request can consume.
General guidance for the resource management errors class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.0= 3.0= 3.1all versions= 2.1= 3.0= 4.0= 3.0= 4.0= core_1.0= core_2.0= core_3.0= core_4.0= 7.3= 9.0= 2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade xpdf and related packages (poppler, kpdf, pdftohtml, cups, libextractor, tetex-base) to versions that include the CVE-2005-3625 patch. For RHEL 2.1/3.0/4.0, use RHN updates. For Fedora Core 1-4, use respective updates. For SUSE, use the patches referenced in the January 2006 SUSE security ad
- Identify the affected Xpdf-related packages installed on the system (xpdf, poppler, kpdf, pdftohtml, cups, libextractor, tetex-base)
- For Red Hat Enterprise Linux systems, apply updates via RHN or yum update xpdf poppler cups
- For Fedora Core systems, apply updates via yum or up2date for the respective core version
- For Debian systems, apply updates via apt-get update && apt-get upgrade for xpdf-related packages
- For SUSE systems, apply updates as referenced in the SUSE security announcement: http://lists.suse.com/archive/suse-security-announce/2006-Jan/0001.html
- Verify the fix by confirming the packages are updated to versions that include the patch for the infinite loop vulnerability
- Restart any services using the affected libraries (CUPS, PDF viewers) after updating
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3625 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- lists.suse.com
- scary.beasts.org
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- lists.suse.com
- rhn.redhat.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- www.debian.org
- www.debian.org
- www.debian.org
- www.gentoo.org
- www.kde.org
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.securityfocus.com
- scary.beasts.org
- ftp.sco.com
- patches.sgi.com
- patches.sgi.com
- patches.sgi.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- slackware.com
- slackware.com
- sunsolve.sun.com
- www.debian.org
- www.debian.org
- www.debian.org
- www.debian.org
- www.debian.org
- www.debian.org
- www.gentoo.org
- www.mandriva.com
- www.mandriva.com
- www.mandriva.com
- www.mandriva.com
- www.mandriva.com
- www.mandriva.com
- www.mandriva.com
- www.mandriva.com
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.securityfocus.com
- www.securityfocus.com
- www.trustix.org
- www.vupen.com
- www.vupen.com
- exchange.xforce.ibmcloud.com
- oval.cisecurity.org
- usn.ubuntu.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-3625 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data