CVE-2017-10925
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 might allow attackers to cause a denial of service or possibly have unspecified other impact via a crafted .fpx file, related to "Data from Faulting Address is used as one or more arguments in a subsequent Function Call starting at FPX!FPX_GetScanDevicePropertyGroup+0x000000000000b3ae."
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 · moderate confidenceIrfanView 4.44 32-bit with FPX Plugin 4.47 contains a memory corruption vulnerability when parsing crafted .fpx files. The vulnerability occurs because data from a faulting address is used as arguments in a subsequent function call within FPX_GetScanDevicePropertyGroup, allowing attackers to potentially achieve code execution or cause denial of service.
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.
-
Check if IrfanView is installedLook for IrfanView in typical installation locations: C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView, or search for i_view32.exe using 'where i_view32' in Command PromptAffected if IrfanView executable is found on the system
-
Verify IrfanView version is 4.44Right-click i_view32.exe, select Properties, then look at the Details tab for Product Version, or run 'i_view32.exe /?' and check the version stringAffected if Product version shows exactly 4.44 (the affected version)
-
Locate the FPX pluginNavigate to the IrfanView installation folder and look for a Plugins subfolder, then check for fpx.dll or similar FPX-related filesAffected if FPX plugin file (such as fpx.dll) exists in the Plugins folder
-
Verify FPX plugin version is 4.47Right-click the FPX plugin file, select Properties, then Details tab to check File Version or Product VersionAffected if Plugin version shows exactly 4.47 (the affected version)
-
Confirm FPX plugin is enabledOpen IrfanView, go to Options > Settings > Plugins, or check registry key HKCU\Software\IrfanView\PlugIns for enabled FPX supportAffected if FPX plugin is listed as loaded/enabled in IrfanView plugin settings
User is affected if IrfanView 4.44 with FPX plugin 4.47 is installed and the FPX plugin is enabled, allowing crafted .fpx files to trigger the memory corruption in FPX_GetScanDevicePropertyGroup.
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 dataAvoid opening untrusted .fpx files in affected IrfanView installations. Update to patched versions of the FPX plugin when available, or disable the FPX plugin if not required.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10925 — 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-10925 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