CVE-2017-9878
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 · uneditedIrfanView version 4.44 (32bit) with FPX Plugin 4.46 allows attackers to execute arbitrary code or cause a denial of service via a crafted .fpx file, related to a "Read Access Violation on Control Flow starting at FPX!FPX_GetScanDevicePropertyGroup+0x000000000000c99a."
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 confidenceBuffer read vulnerability (access violation) in IrfanView's FPX plugin when parsing crafted .fpx files, allowing attackers to potentially execute arbitrary code or cause denial of service via memory corruption.
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= 4.44= 4.46CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Check IrfanView installation statusLocate IrfanView installation directory (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView). Verify iview64.exe or i_view32.exe exists.Affected if IrfanView is installed on the system
-
Determine IrfanView versionRight-click iview64.exe or i_view32.exe, select Properties, check the Details tab for Product Version. Alternatively, launch IrfanView and go to Help > About IrfanView.Affected if Product version is 4.44 or lower (or any version prior to patched release)
-
Locate FPX plugin fileNavigate to the IrfanView installation directory, then to the Plugins subfolder. Look for FPX.dbg, fpx.dll, or similar FPX-related files.Affected if FPX plugin file exists in the Plugins folder
-
Check FPX plugin versionIf FPX plugin file exists, right-click the fpx.dll file, select Properties, check Details tab for File Version. Alternatively, check the plugin version within IrfanView via Options > Plugins/Extensions.Affected if Plugin version is 4.46 or lower (or any version prior to patched release)
-
Verify FPX file association or plugin loadingOpen IrfanView, attempt to open a .fpx file or check Options > Plugins/Extensions to see if FPX plugin is loaded and enabled.Affected if FPX plugin is loaded and enabled in IrfanView
System is affected if IrfanView version 4.44 or lower AND FPX plugin version 4.46 or lower are installed with the FPX plugin enabled, allowing parsing of .fpx files.
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 IrfanView and FPX plugin to patched versions; avoid opening untrusted .fpx files until patched.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9878 — 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-9878 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