dbcve.org
FpxApplication · Irfanview

CVE-2017-8370

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.45 allows remote attackers to execute arbitrary code or cause a denial of service (Heap Corruption and application crash) in processing a FlashPix (.FPX) file, a different vulnerability than CVE-2017-7721.

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

The FPX (FlashPix) plugin 4.45 in IrfanView 4.44 (32-bit) contains a heap corruption vulnerability when parsing specially crafted .FPX files. This memory corruption can be exploited by remote attackers to achieve arbitrary code execution or cause a denial of service through application crash.

MitigationUpdate the FPX plugin to a patched version or disable the FPX plugin in IrfanView if not required. Avoid opening untrusted .FPX files from unknown sources.

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

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. Locate IrfanView installation
    Check if IrfanView is installed on the system. Common installation paths include C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView. Verify the presence of i_view32.exe or i_view64.exe.
    Affected if IrfanView is installed on the system.
  2. Check IrfanView version
    Right-click on the IrfanView executable (i_view32.exe or i_view64.exe), select Properties, and view the File Version in the Details tab. Alternatively, run IrfanView and check Help > About IrfanView.
    Affected if The installed version is 4.44.
  3. Locate and verify FPX plugin version
    Navigate to the Plugins folder within the IrfanView installation directory (typically Plugins\). Locate the FPX plugin file (fpx.dll or similar). Right-click and view File Version in Properties > Details.
    Affected if The FPX plugin version is 4.45.
  4. Confirm FPX plugin is loaded
    Open IrfanView and go to Options > Properties/Settings > Plugins. Verify that the FPX plugin is listed as enabled, or check if .FPX files can be opened in IrfanView.
    Affected if The FPX plugin is enabled and able to process .FPX files.

A user is affected if they have IrfanView 4.44 installed with FPX plugin version 4.45 and the FPX plugin is enabled, allowing them to open potentially malicious .FPX 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 disable the FPX plugin in IrfanView if not required. Avoid opening untrusted .FPX files from unknown sources.

Fix this in Fpx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8370 — 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-8370 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