CVE-2017-12921
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 · uneditedPFileFlashPixView::GetGlobalInfoProperty in f_fpxvw.cpp in libfpx 1.3.1_p6 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted fpx image.
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 confidenceA NULL pointer dereference vulnerability exists in libfpx 1.3.1_p6 in the PFileFlashPixView::GetGlobalInfoProperty function within f_fpxvw.cpp. When processing a specially crafted FPX (FlashPix) image file, the application attempts to dereference a NULL pointer, causing a denial of service (application crash).
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= 1.3.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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Identify if libfpx is installedRun 'dpkg -l | grep libfpx' on Debian-based systems, 'rpm -qa | grep fpx' on RHEL-based systems, or 'pkg-config --modversion libfpx' if pkg-config is available. Check common library paths like /usr/lib/ for files named libfpx.so or libfpx.a.Affected if libfpx version 1.3.1 is installed
-
Find applications linking to libfpxUse 'ldd' on binaries in common image viewers or graphics applications, or run 'ldconfig -p | grep fpx' to list programs that depend on libfpx.Affected if any application on the system links against libfpx library
-
Determine if FPX image support is enabledCheck application documentation or configuration for FPX (FlashPix) image format support. Some image viewers may have FPX support compiled in but disabled by default.Affected if FPX format support is enabled in any libfpx-dependent application
-
Check for FPX file processing capabilityAttempt to identify if any application on the system can process .fpx files by checking file associations or running 'file' command on sample FPX files if any exist on the system.Affected if applications on the system can open and process FPX image files
A user is affected if libfpx version 1.3.1 is installed AND applications using this library have FPX image processing capability enabled, allowing specially crafted FPX files to trigger the NULL pointer dereference.
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 dataAvoid opening untrusted or unknown FPX image files with applications using libfpx. If available, apply any vendor patches for libfpx that address this NULL pointer dereference in the GetGlobalInfoProperty function.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12921 — 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-2017-12921 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