CVE-2017-9916
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 TOOLS Plugin 4.50 might allow attackers to cause a denial of service or possibly have unspecified other impact via a crafted file, related to "Data from Faulting Address controls Branch Selection starting at ntdll_77df0000!RtlFreeHandle+0x00000000000001b6."
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 confidenceA memory corruption vulnerability in IrfanView 4.44 (32-bit) with TOOLS Plugin 4.50 allows attackers to cause denial of service or potentially achieve code execution via a crafted file. The vulnerability stems from improper handling of file data during parsing, leading to a faulting address in ntdll.dll that can control branch selection.
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.50CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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.
-
Verify IrfanView 32-bit installationCheck if IrfanView 32-bit version is installed on the system. Look for IrfanView installation directory (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView). Verify the executable is the 32-bit version (i_view32.exe).Affected if IrfanView 32-bit (i_view32.exe) is installed on the system.
-
Check TOOLS Plugin versionNavigate to the IrfanView plugins folder (usually C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins) and locate the tools.dll file. Right-click the file and select Properties, then check the Version tab for the file version.Affected if TOOLS Plugin (tools.dll) version is exactly 4.50.
-
Confirm plugin is loadedOpen IrfanView, go to Menu > Options > Plugins. Verify that the TOOLS plugin is enabled and listed in the plugins dialog.Affected if The TOOLS plugin is enabled and loaded by IrfanView.
-
Identify processed filesReview recently opened image files, particularly those from untrusted or unknown sources. Check file access logs or the application's recent files list for any crafted malicious image files that may have been opened.Affected if A crafted malicious file has been opened or processed using the TOOLS plugin functionality.
A system is affected if it has IrfanView 32-bit with TOOLS Plugin version 4.50 installed and the plugin is enabled, allowing crafted files to trigger the memory corruption vulnerability.
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 TOOLS Plugin to the latest patched versions. Avoid opening untrusted or crafted image files from unknown sources.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9916 — 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-9916 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