CVE-2015-6673
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 · uneditedUse-after-free vulnerability in Decoder.cpp in libpgf before 6.15.32.
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 · moderate confidenceA use-after-free vulnerability exists in Decoder.cpp in the libpgf library in versions prior to 6.15.32. This memory corruption flaw allows attackers to potentially execute arbitrary code or cause a denial of service by referencing memory that has already been freed.
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 data<= 6.14.12CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate libpgf library on the systemSearch for libpgf library files (typically named libpgf.so on Linux or libpgf.dll on Windows) using commands like 'find / -name "libpgf*"' on Linux or checking standard library directories on Windows.Affected if The library file exists on the system, indicating libpgf is installed.
-
Determine installed libpgf versionUse system package management tools (dpkg -l, rpm -qi, or similar) to query the installed libpgf package version, or inspect version metadata embedded in the library file if package tools are unavailable.Affected if The displayed version number is 6.14.12 or lower.
-
Verify libpgf is in use by the applicationIdentify applications or processes that link against libpgf by examining application dependencies (ldd on Linux, or checking import tables on Windows) or reviewing application documentation/configurations that reference libpgf.Affected if Any application or service loads or links to the vulnerable libpgf library.
-
Confirm Decoder.cpp component is activeReview application logs, debugging output, or network traffic if the application processes PGF-encoded images or documents, as Decoder.cpp handles PGF decoding functionality.Affected if The application processes PGF image formats or uses PGF decoding capabilities.
The system is affected if libpgf version 6.14.12 or lower is installed and any application uses the PGF decoding functionality provided by Decoder.cpp.
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.
dbcve · scopedUpgrade libpgf to version 6.15.32 or later to remediate the use-after-free vulnerability. Inventory all applications and components using libpgf to ensure complete coverage.
6.15.32 or later
- 1. Identify the current version of libpgf installed in your system
- 2. Download libpgf version 6.15.32 or later from the official source (sourceforge.net/projects/libpgf)
- 3. Compile and install the new version according to the project's build instructions
- 4. Verify the installation was successful and the new version is active
- 5. Rebuild any applications that link against libpgf to ensure they use the updated library
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6673 — 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-2015-6673 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