CVE-2017-9884
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 cause a denial of service or possibly have unspecified other impact via a crafted .fpx file, related to "Data from Faulting Address controls Branch Selection starting at ntdll_77df0000!RtlpCoalesceFreeBlocks+0x00000000000001b6."
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 confidenceIrfanView 4.44 (32-bit) with FPX Plugin 4.46 suffers from a memory corruption vulnerability when parsing crafted .fpx (FlashPix) image files. The vulnerability manifests in ntdll's heap management (RtlpCoalesceFreeBlocks), where data from the faulting address controls branch selection, indicating the attacker can influence code execution flow through heap 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.
-
Confirm IrfanView installation and versionLocate IrfanView executable (typically in Program Files) and check file properties or run with /? flag to display version, or inspect registry under HKLM\SOFTWARE\IrfanViewAffected if Installed version is exactly 4.44 (32-bit)
-
Locate FPX plugin fileFind fpx.dll in the IrfanView plugins folder (typically \IrfanView\Plugins\)Affected if fpx.dll plugin file is present in the plugins directory
-
Verify FPX plugin versionRight-click fpx.dll file in plugins folder, select Properties, and check the File Version under Details tabAffected if Plugin version is exactly 4.46
-
Confirm 32-bit IrfanView is in useCheck the IrfanView executable filename - 32-bit versions are typically named irfanview.exe while 64-bit are named irfanview64.exeAffected if The installed executable is irfanview.exe (32-bit)
-
Determine if FPX file handling is enabledIn IrfanView, go to Options > Settings > Plugins and verify the FPX plugin is loaded/checked, or check that fpx.dll is not renamed or moved out of the plugins folderAffected if FPX plugin is enabled and fpx.dll loads normally
User is affected if running IrfanView 4.44 (32-bit) with FPX plugin version 4.46, and the FPX plugin is enabled to handle .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 the FPX plugin to patched versions; avoid opening untrusted .fpx files until patches are applied.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9884 — 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-9884 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