CVE-2017-9885
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 is used as one or more arguments in a subsequent Function Call starting at FPX!FPX_GetScanDevicePropertyGroup+0x0000000000006a98."
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 confidenceMemory corruption vulnerability in IrfanView's FPX (FlashPix) plugin 4.46 when processing crafted .fpx files. The vulnerability occurs when data from an invalid memory address (faulting address) is used as arguments in a subsequent function call within FPX_GetScanDevicePropertyGroup, leading to potential code execution or denial of service.
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 the IrfanView executable (typically in Program Files) and check its version property, or run 'irfanview.exe /?' or check file properties to obtain the installed version number.Affected if The installed IrfanView version is 4.44 (the affected version listed in the CVE).
-
Locate the FPX plugin fileFind the FPX plugin file (typically named FPX.dll or similar) within the IrfanView plugins directory (commonly i_plugins folder).Affected if The FPX plugin file exists in the IrfanView plugins directory, indicating the plugin is installed.
-
Determine FPX plugin versionCheck the version property of the FPX plugin file (right-click file, select Properties, view Version tab) to obtain its version number.Affected if The FPX plugin version is 4.46 (the affected version listed in the CVE).
-
Verify FPX plugin is loaded by IrfanViewOpen IrfanView, go to menu Image > Information, or check the Plugins section in IrfanView options to confirm the FPX plugin is active and recognized.Affected if The FPX plugin appears as enabled or loaded in IrfanView, meaning the vulnerability can be triggered when opening malicious .fpx files.
You are affected if IrfanView version 4.44 is installed with FPX plugin version 4.46 and the plugin is enabled, allowing crafted .fpx files to trigger the memory corruption in FPX_GetScanDevicePropertyGroup.
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 unverified .fpx files in vulnerable IrfanView installations. Update to patched versions of the FPX plugin when available, or remove/disable the plugin if not needed.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9885 — 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-9885 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