CVE-2017-14693
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 .djvu file, related to "Data from Faulting Address controls Branch Selection starting at DJVU!GetPlugInInfo+0x000000000001c613."
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 DJVU plugin (GetPlugInInfo function). When processing a specially crafted .djvu file, the application suffers from a flaw where 'Data from Faulting Address controls Branch Selection,' allowing attackers to potentially hijack control flow for denial of service or possibly achieve 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.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 installation and versionOpen IrfanView, go to Help > About, or right-click the IrfanView executable (i_view32.exe or i_view64.exe) in the installation directory and select Properties to view the File Version. Compare against version 4.44.Affected if The installed version is exactly 4.44 (32-bit)
-
Locate the DJVU plugin fileNavigate to the IrfanView installation folder and locate the 'plugins' or 'plugins32' subdirectory. Look for a DjVu-related DLL file (such as DjVu.dll, DjVuPlugin.dll, or similar).Affected if A DJVU plugin DLL file exists in the plugins directory
-
Verify if the DJVU plugin is loadedOpen IrfanView, go to Properties > Plugins, or check the Plugins menu to see if the DJVU plugin is listed and enabled. The vulnerability is triggered through the GetPlugInInfo function.Affected if The DJVU plugin is listed as loaded or enabled in IrfanView
-
Check for .djvu file associationCheck if .djvu file types are associated with IrfanView by right-clicking any .djvu file in Windows Explorer, selecting Properties, and viewing the 'Opens with' field.Affected if IrfanView is set as the default handler for .djvu files
You are affected if IrfanView version 4.44 is installed AND the DJVU plugin is present and enabled, with the application configured to open .djvu 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 dataAvoid opening untrusted or unverified .djvu files in IrfanView until an official vendor patch is released. Consider restricting file type associations or using application sandboxing as a compensating control.
- Consultation3.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,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14693 — 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-14693 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