CVE-2017-9921
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!LdrpResGetMappingSize+0x00000000000003cc."
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 TOOLS Plugin 4.50 contains a memory corruption vulnerability when parsing crafted files. The vulnerability allows attackers to control branch selection via corrupted memory during file processing, potentially leading to denial of service or arbitrary code execution.
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.
-
Determine IrfanView versionOpen IrfanView, go to Help > About, or right-click the IrfanView executable and view Properties > Details to see the version numberAffected if The installed version is exactly 4.44 (based on the affected versions listed)
-
Locate the TOOLS pluginNavigate to the IrfanView plugins directory (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins) and look for a file related to TOOLS pluginAffected if A TOOLS plugin file exists in the plugins directory (presence indicates the vulnerable component is installed)
-
Determine TOOLS plugin versionIf the TOOLS plugin DLL is found, right-click the file and view Properties > Details to find the version informationAffected if The TOOLS plugin version is exactly 4.50 (the specific affected version listed)
-
Check if plugins folder is loaded by defaultOpen IrfanView and verify that plugins are automatically loaded on startup (default behavior), or check IrfanView settings under Options > Properties/Settings > PluginsAffected if Plugins load automatically and the TOOLS plugin is present in the plugins directory
You are affected if both the TOOLS plugin version 4.50 OR IrfanView version 4.44 is installed, and the TOOLS plugin is present and loaded in the IrfanView plugins directory.
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 the TOOLS Plugin to a patched version beyond 4.50, or upgrade IrfanView to a version that includes the fixed plugin. Avoid opening untrusted files in affected IrfanView installations.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9921 — 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-9921 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