CVE-2017-9873
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!GetPlugInInfo+0x0000000000012bf2."
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 memory corruption vulnerability exists in IrfanView's FPX (FlashPix) plugin version 4.46 when processing specially crafted .fpx image files. The flaw manifests as a read access violation on control flow at FPX!GetPlugInInfo+0x0000000000012bf2, allowing attackers to potentially hijack execution flow and achieve arbitrary code execution or cause a 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.
-
Verify IrfanView installation and versionLocate the IrfanView executable (typically in C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView). Right-click on i_view32.exe or i_view64.exe, select Properties, and check the Details tab for the Product version.Affected if The installed IrfanView version is 4.44 exactly.
-
Locate the FPX plugin fileNavigate to the IrfanView Plugins folder (usually C:\Program Files\IrfanView\Plugins or within the IrfanView directory). Look for a file named FPX.fpx or similar FPX-related plugin file.Affected if The FPX plugin file exists in the Plugins folder.
-
Determine FPX plugin versionRight-click on the FPX plugin file (FPX.fpx) in the Plugins folder, select Properties, and check the Details tab for the File version or Product version.Affected if The installed FPX plugin version is 4.46 exactly.
-
Confirm FPX plugin is loaded by IrfanViewOpen IrfanView, go to Menu > Image Information or press I on an image to verify IrfanView is functioning. The vulnerability triggers when IrfanView attempts to open a malicious .fpx file using the FPX plugin.Affected if The FPX plugin is present and IrfanView can be used to open image files, meaning the plugin is available for exploitation.
A user is affected if IrfanView version 4.44 is installed with FPX plugin version 4.46, and the FPX plugin remains available for processing .fpx image 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 the FPX plugin to the latest version available from IrfanView, or disable the FPX plugin entirely if not required, until the patch can be applied.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9873 — 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-9873 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