CVE-2017-14539
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 allows attackers to cause a denial of service or possibly have unspecified other impact via a crafted .svg file, related to "Data from Faulting Address controls Branch Selection starting at image00000000_00400000+0x000000000011d767."
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 contains a memory corruption vulnerability in its SVG file parsing functionality. The vulnerability allows attackers to control branch selection through data from a faulting address (write-what-where condition), which can cause a denial of service or potentially achieve arbitrary code execution when a user opens a specially crafted SVG file.
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.44CVSS 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.
-
Confirm IrfanView is installedCheck for IrfanView installation by looking in Program Files (x86) for IrfanView or by running 'irfanview' in command prompt to see if it's in PATHAffected if IrfanView is not installed on the system
-
Identify installed IrfanView versionRight-click the IrfanView executable (irfanview.exe), select Properties, and check the Details tab for the version number, or run 'irfanview.exe /?' to see version infoAffected if The version displayed is exactly 4.44
-
Verify 32-bit installationCheck the file path: 32-bit IrfanView is typically installed in 'C:\Program Files (x86)\IrfanView' while 64-bit is in 'C:\Program Files\IrfanView'. Alternatively, right-click irfanview.exe, go to Compatibility tab or use a tool like ExeInfoPE to confirm architectureAffected if The installed version is the 32-bit (x86) build of IrfanView 4.44
-
Check for SVG pluginNavigate to the IrfanView plugins folder (usually C:\Program Files (x86)\IrfanView\Plugins) and look for svg.dll or similar SVG-related plugin filesAffected if SVG parsing capability exists through the svg.dll plugin
You are affected if IrfanView version 4.44 (32-bit) with SVG parsing capability is installed and users may open untrusted SVG files.
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 unsolicited SVG files in IrfanView 4.44. If available, apply vendor patches or upgrade to a newer version of IrfanView that addresses this vulnerability. Consider using alternative image viewers for handling untrusted SVG content as a compensating control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14539 — 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-14539 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