CVE-2017-9530
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) might allow attackers to cause a denial of service or execute arbitrary code via a crafted file, related to "Data from Faulting Address is used as one or more arguments in a subsequent Function Call starting at ntdll_77df0000!LdrpResCompareResourceNames+0x0000000000000150."
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) allows attackers to cause denial of service or execute arbitrary code via a crafted file. The vulnerability occurs during Windows loader resource name comparison (ntdll!LdrpResCompareResourceNames), where data from a faulting address is improperly used as function arguments, indicating a buffer or memory handling error in image file parsing.
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.
-
Identify installed IrfanView versionOpen IrfanView and go to Help > About, or right-click irfanview.exe and select Properties > Details to see the version numberAffected if Version is 4.44 (32-bit)
-
Confirm IrfanView architectureCheck if the installed IrfanView is the 32-bit version by looking at the program files folder - 32-bit typically installs to C:\Program Files (x86)\IrfanView, while 64-bit installs to C:\Program Files\IrfanViewAffected if Installed in Program Files (x86) folder or running as 32-bit process
-
Check IrfanView Tools version if installedLook for IrfanView Tools in the installed programs list (Control Panel > Programs and Features) or check the version of i_view32.exe or i_view64.exe in the IrfanView folderAffected if IrfanView Tools version is 4.50 or lower
-
Verify file association handlingCheck if IrfanView is set as the default handler for image formats by reviewing File > Properties > File associations in IrfanView, or through Windows Default Programs settingsAffected if IrfanView is the default handler for image file types and may automatically open untrusted files
You are affected if IrfanView 4.44 (32-bit) or IrfanView Tools version 4.50 or lower is installed, and the application processes image 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 dataDo not open untrusted or unknown files in IrfanView. Apply vendor patches when available. Implement application sandboxing, restrict file type associations, or deploy endpoint protection to block exploitation of unpatched IrfanView instances.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9530 — 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-9530 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