CVE-2017-15745
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.50 - 64bit with CADImage plugin version 12.0.0.5 allows attackers to cause a denial of service or possibly have unspecified other impact via a crafted .dwg file, related to "Data from Faulting Address controls Branch Selection starting at CADIMAGE+0x000000000002ca2e."
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 · high confidenceMemory corruption vulnerability in IrfanView's CADImage plugin (v12.0.5005) when parsing specially crafted .dwg files. The 'Data from Faulting Address controls Branch Selection' indicates the vulnerability allows an attacker to potentially influence program execution flow, possibly leading to code execution beyond just denial of service.
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.50= 12.0.0.5CVSS 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.
-
Confirm IrfanView installationCheck if IrfanView is installed by looking for the executable (i_view32.exe or i_view64.exe) in Program Files or a custom installation directoryAffected if IrfanView is installed on the system
-
Locate CADImage pluginSearch for cadimage.dll in the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or similar)Affected if The CADImage plugin file (cadimage.dll) exists in the IrfanView plugins directory
-
Check CADImage plugin versionRight-click on cadimage.dll, select Properties, then go to the Details tab to view the File VersionAffected if The CADImage plugin version is 12.0.5005 exactly, or falls within the 12.0.0.5 version range
-
Verify IrfanView base versionOpen IrfanView and go to Help > About, or check the i_view32.exe/i_view64.exe file properties for the versionAffected if IrfanView version is 4.50
-
Check .dwg file associationsLook in Windows Registry under HKEY_CLASSES_ROOT\.dwg or check file type associations to see if IrfanView is set as the handler for .dwg filesAffected if IrfanView is associated as the default program for opening .dwg files
A user is affected if they have CADImage plugin version 12.0.5005 (or 12.0.0.5) installed with IrfanView and use IrfanView to open .dwg files, either by default association or manual opening.
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 CADImage plugin to vendor-supplied patch, or remove/disable the plugin if unnecessary. Avoid opening untrusted or unknown .dwg files in IrfanView until patch is applied.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15745 — 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-15745 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