CVE-2017-10924
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 4.44 (32bit) with FPX Plugin 4.47 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!FPX_GetScanDevicePropertyGroup+0x000000000000a529."
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 User Mode Write Access Violation vulnerability exists in IrfanView 4.44 (32-bit) with FPX Plugin 4.47 when parsing specially crafted FlashPix (.fpx) image files. The flaw occurs at FPX_GetScanDevicePropertyGroup in the FPX plugin, allowing attackers to achieve arbitrary code execution or cause a denial of service via malicious .fpx files.
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.47CVSS 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.
-
Determine IrfanView versionOpen IrfanView and go to Help > About, or check the executable file properties of irfanview.exeAffected if The displayed version is exactly 4.44 (32-bit version)
-
Determine FPX plugin versionLocate the FPX plugin file (typically fpx.dll) in the IrfanView plugins directory and check its file properties, or view plugin version via IrfanView > Plugins > Plugin InfoAffected if The FPX plugin version is exactly 4.47
-
Verify FPX plugin is present and enabledCheck if the FPX plugin DLL exists in the plugins folder and is recognized by IrfanView (visible in Plugins menu or Plugin Info window)Affected if The FPX plugin is installed and loaded by IrfanView
-
Confirm 32-bit installationCheck the file properties of irfanview.exe to confirm it is a 32-bit executable, or check the program files directory (Program Files x86 vs Program Files)Affected if IrfanView is the 32-bit version installed
You are affected if you have IrfanView version 4.44 (32-bit) with FPX plugin version 4.47 present and enabled, as this specific combination triggers the vulnerability when parsing malicious .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 dataUpdate IrfanView and FPX plugin to latest patched versions; avoid opening untrusted .fpx files; consider disabling or removing the FPX plugin if not required.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10924 — 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-10924 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