CVE-2017-7721
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 before 4.45 has an Access Violation and crash in processing a FlashPix (.FPX) file.
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 confidenceBuffer overflow or memory corruption vulnerability in IrfanView's FPX (FlashPix) plugin when parsing specially crafted .FPX files, leading to an access violation and application crash. The issue affects FPX Plugin versions before 4.45 when used with IrfanView 4.44 32-bit.
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.44CVSS 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.
-
Identify IrfanView installation path and versionLocate IrfanView installation (typically C:\Program Files\IrfanView\i_view32.exe or C:\Program Files (x86)\IrfanView\i_view32.exe). Right-click the executable, select Properties, and check the File Version field under the Details tab. Alternatively, run 'i_view32.exe /?' or check Help > About in the application.Affected if The File Version shows 4.44 (exactly). Versions before or after 4.44 are not affected by this specific CVE.
-
Locate and verify the FPX plugin versionNavigate to the IrfanView plugins folder (usually C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins). Find the FPX plugin file (typically FPX.dll). Right-click the file, select Properties, and check the File Version under the Details tab.Affected if The FPX plugin version is 4.44 or earlier. Versions 4.45 and later are patched. If the plugin is not present, this specific vulnerability does not apply.
-
Confirm the FPX plugin is registered and loadableOpen IrfanView and go to menu: Image > Information, or attempt to open a legitimate .FPX file. If the application can load .FPX files without error, the plugin is active. Also check if FPX.dll appears in the plugins folder.Affected if The FPX plugin is present and can be used to open FlashPix files. If the plugin is removed or disabled, the attack surface for this specific vulnerability is not present.
-
Verify architecture matches vulnerable configurationCheck if the IrfanView installation is 32-bit. This is indicated by the presence of i_view32.exe (32-bit) versus i_view64.exe (64-bit). The CVE specifically notes it affects the 32-bit version of IrfanView 4.44.Affected if Running 32-bit IrfanView 4.44 with FPX plugin <= 4.44. 64-bit versions or other IrfanView versions are not affected by this specific CVE.
You are affected if you are running IrfanView 4.44 (32-bit) with an FPX plugin version 4.44 or earlier, and the FPX plugin is installed and functional for opening .FPX 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 dataUpgrade the FPX Plugin to version 4.45 or later. Avoid opening untrusted or unknown FlashPix (.FPX) files until the update is applied.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7721 — 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-7721 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