CVE-2017-9919
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 execute arbitrary code via a crafted file, related to "Data from Faulting Address controls Branch Selection starting at ntdll_77df0000!LdrpResCompareResourceNames+0x0000000000000087."
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 confidenceMemory corruption vulnerability in IrfanView TOOLS Plugin 4.50 when processing crafted files. The vulnerability allows an attacker to control branch selection through faulting address data, potentially achieving denial of service or arbitrary code execution. This is a classic memory corruption issue in the file parsing logic of the TOOLS plugin.
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.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
- 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 installation in the default location: C:\Program Files\IrfanView\i_view32.exe, or check the Windows registry under HKLM\SOFTWARE\IrfanView or HKLM\SOFTWARE\WOW6432Node\IrfanView for the InstallPath value.Affected if IrfanView is not installed on the system.
-
Identify the installed IrfanView versionRight-click the IrfanView executable (i_view32.exe), select Properties, and check the Details tab for the File Version. Alternatively, run IrfanView and go to Help > About to view the version number.Affected if The installed version equals 4.44.
-
Check if the TOOLS plugin is installedNavigate to the IrfanView installation directory and look for a Plugins subfolder. Check for a tools.dll or similar TOOLS plugin file. Common path: C:\Program Files\IrfanView\Plugins\tools.dllAffected if The TOOLS plugin file exists in the Plugins folder.
-
Identify the TOOLS plugin versionRight-click the tools.dll file in the Plugins folder, select Properties, and check the Details tab for the File Version. The version is displayed there.Affected if The TOOLS plugin version equals 4.50.
-
Determine if TOOLS plugin functionality is in useOpen IrfanView and check if the TOOLS menu is available, or attempt to access features that invoke the TOOLS plugin functionality when processing image files.Affected if The TOOLS menu or plugin features are accessible and can be used to process files.
You are affected if IrfanView version 4.44 and TOOLS plugin version 4.50 are installed, and you use the TOOLS plugin to open files from untrusted sources.
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 IrfanView and the TOOLS Plugin to versions that include the security patch. Avoid opening untrusted or unknown files in IrfanView until the patch is applied.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9919 — 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-9919 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