CVE-2006-0746
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 · uneditedCertain patches for kpdf do not include all relevant patches from xpdf that were associated with CVE-2005-3627, which allows context-dependent attackers to exploit vulnerabilities that were present in CVE-2005-3627.
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 analysis · high confidencekpdf, the KDE PDF viewer, was shipped with patches that did not include all relevant security patches from the upstream xpdf project that were associated with CVE-2005-3627. This incomplete patching allowed context-dependent attackers to exploit PDF parsing vulnerabilities that had been fixed in xpdf but not fully ported to kpdf.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 dataall versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm kpdf installationRun 'dpkg -l kpdf' (Debian/Ubuntu), 'rpm -q kpdf' (RHEL/Fedora), or check your package manager for the kpdf packageAffected if kpdf is installed on the system
-
Identify kpdf versionRun 'kpdf --version' or use your package manager to query the installed kpdf version (e.g., 'dpkg -s kpdf' or 'rpm -qi kpdf')Affected if The installed version is any version of kpdf that predates the complete backporting of CVE-2005-3627 patches
-
Check for CVE-2005-3627 patch statusInspect the kpdf source code or binary for the presence of the CVE-2005-3627 fixes in PDF parsing routines, or check vendor security advisories for your distribution for mention of CVE-2005-3627 being addressed in kpdfAffected if The CVE-2005-3627 security patches were not applied to the kpdf build
-
Verify PDF processing is enabledConfirm that kpdf is configured to render PDF documents (default behavior) - no special configuration required as PDF rendering is the core functionAffected if kpdf can open and parse arbitrary PDF files
A system is affected if kpdf is installed and its version lacks the complete set of CVE-2005-3627 security patches from the upstream xpdf project.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate kpdf to a version that includes the complete set of xpdf security patches, or apply the missing patches from CVE-2005-3627 to the kpdf codebase.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0746 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-0746 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