CVE-2017-15740
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 execute arbitrary code or cause a denial of service via a crafted .dwg file, related to "Data from Faulting Address controls Code Flow starting at CADIMAGE+0x000000000033228e."
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 64-bit version 4.50 with CADImage plugin version 12.0.0.5 contains a memory corruption vulnerability when parsing crafted .dwg files. The vulnerability allows an attacker to control code flow through data at a faulting address (CADIMAGE+0x000000000033228e), enabling arbitrary code execution or 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 version and architectureOpen IrfanView and go to Help > About, or right-click irfanview.exe and select Properties > Details to view the version number. Verify it is version 4.50 and the 64-bit variant.Affected if The installed version is IrfanView 4.50 64-bit
-
Confirm CADImage plugin versionLocate the CADImage plugin file (typically named CADImage.dll or similar in the IrfanView Plugins folder). Right-click the file, select Properties > Details to view the version. Alternatively, open IrfanView and go to Help > About Plugins to list loaded plugins and their versions.Affected if The CADImage plugin version is 12.0.0.5
-
Verify CADImage plugin is present and enabledCheck that the CADImage plugin DLL exists in the IrfanView Plugins directory and is not renamed, moved, or deleted. Also verify it appears in the list of loaded plugins when IrfanView starts.Affected if The CADImage plugin file exists and is being loaded by IrfanView
-
Check if .dwg file handling is associated with IrfanViewExamine if .dwg file associations or context menu entries point to IrfanView, or if users commonly open .dwg files directly in IrfanView for thumbnail previewing.Affected if Users open or preview .dwg files using IrfanView with the CADImage plugin
You are affected if you have IrfanView 4.50 64-bit with CADImage plugin version 12.0.0.5 installed and users open .dwg files in IrfanView.
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 dataUsers should avoid opening untrusted .dwg files in IrfanView with the CADImage plugin until an updated version is available. Consider disabling or removing the CADImage plugin if not required for legitimate workflows.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15740 — 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-15740 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