dbcve.org
IrfanviewApplication

CVE-2017-9533

HIGH · 7.8 CVSS v3.0 Published 2017-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
IrfanView 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 "User Mode Write AV starting at FPX!DE_Decode+0x0000000000000a9b."

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 confidence

A memory corruption vulnerability exists in the FPX (FlashPix) plugin 4.46 for IrfanView 4.44 (32-bit). Attackers can trigger a user-mode write access violation in the DE_Decode function by parsing a specially crafted .fpx file, leading to arbitrary code execution or denial of service.

MitigationUpdate the FPX plugin to a patched version or upgrade IrfanView to a version that includes the fixed plugin. Avoid opening untrusted .fpx files until the patch is applied.

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
IrfanviewApplication
Affected:= 4.44
FpxApplication
Affected:= 4.46

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IrfanView version
    Open IrfanView and go to Help > About, or check the executable properties (usually in C:\Program Files\IrfanView\i_view32.exe or C:\Program Files (x86)\IrfanView\i_view32.exe)
    Affected if The installed version is exactly 4.44 (32-bit)
  2. Locate the FPX plugin file
    Find the FPX plugin in the IrfanView plugins folder, typically at C:\Program Files\IrfanView\Plugins\fpx.dll or C:\Program Files (x86)\IrfanView\Plugins\fpx.dll
    Affected if The file fpx.dll exists in the plugins directory
  3. Check FPX plugin version
    Right-click fpx.dll, select Properties, and view the File Version field on the Details tab
    Affected if The plugin file version is listed as 4.46
  4. Verify .fpx file association
    Check if .fpx file type is associated with IrfanView by looking at file associations in IrfanView (Options > File types) or Windows default programs
    Affected if IrfanView is set as the default handler for .fpx files and the plugin is loaded

You are affected if IrfanView 4.44 is installed with the FPX plugin version 4.46 and the plugin is available to process .fpx image files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the FPX plugin to a patched version or upgrade IrfanView to a version that includes the fixed plugin. Avoid opening untrusted .fpx files until the patch is applied.

Fix this in Irfanview Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-9533 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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