CVE-2017-9892
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!RtlpFreeHeap+0x0000000000000393."
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 confidenceHeap corruption vulnerability in IrfanView 4.44 (32-bit) with FPX Plugin 4.46 when parsing crafted .fpx files. The flaw occurs during heap free operations (ntdll!RtlpFreeHeap), indicating a use-after-free or heap overflow condition that can cause denial of service or potentially allow arbitrary code execution.
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.
-
Locate IrfanView installation and versionCheck for i_view32.exe in Program Files (x86) or Program Files folders. Right-click the executable, select Properties, and verify the version on the Details tab. Common paths: C:\Program Files (x86)\IrfanView\i_view32.exe or C:\Program Files\IrfanView\i_view32.exeAffected if Version shows 4.44 (exact match)
-
Confirm 32-bit architectureIn the Properties of i_view32.exe on the General tab, look for '32-bit' designation or check if the file exists in the Program Files (x86) folder, which indicates 32-bit architectureAffected if Running 32-bit version of IrfanView 4.44 (64-bit versions may not be affected)
-
Locate FPX pluginNavigate to the IrfanView Plugins folder (typically C:\Program Files (x86)\IrfanView\Plugins\ or C:\Program Files\IrfanView\Plugins\) and look for FPX-related files such as fpx.dll or i_fpx.dllAffected if FPX plugin file is present in the Plugins directory
-
Verify FPX plugin versionRight-click the FPX plugin DLL file in the Plugins folder, select Properties, and check the version on the Details tab. The plugin version should be 4.46Affected if FPX plugin version is exactly 4.46 (exact match)
-
Confirm plugin is loaded by IrfanViewOpen IrfanView, go to menu Image > Information or check Help > About Plugins. Verify that FPX is listed as an available/loaded pluginAffected if FPX plugin is listed as loaded or enabled in IrfanView
Environment is affected if running IrfanView version 4.44 (32-bit) with FPX plugin version 4.46 present and enabled, and attempting to open crafted .fpx files becomes possible.
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 latest patched versions. Avoid opening untrusted .fpx files from unknown sources. Consider disabling the FPX plugin if not required.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9892 — 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-9892 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