CVE-2017-15744
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 a "Read Access Violation on Control Flow starting at CADIMAGE+0x00000000003d35a7."
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 confidenceThe CADImage plugin version 12.0.0.5 for IrfanView 4.50 (64-bit) contains a memory corruption vulnerability when parsing specially crafted .dwg CAD files. The flaw manifests as a Read Access Violation on control flow, allowing attackers to potentially execute arbitrary code or cause a denial of service by leveraging the uncontrolled memory read.
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 installation and versionLocate the IrfanView executable (commonly in C:\Program Files\IrfanView\ or C:\Program Files (x86)\IrfanView\) and check its file properties to verify version 4.50. Right-click the executable, select Properties, and examine the Details tab for the version number.Affected if The installed version is exactly 4.50 (64-bit edition)
-
Locate the CADImage pluginNavigate to the IrfanView Plugins directory (typically found in the IrfanView installation folder as 'Plugins' or 'Plugins64') and search for files related to CADImage, usually named CadImage.dll or similar CAD-related DLL files.Affected if The CADImage plugin DLL file exists in the Plugins folder
-
Verify CADImage plugin versionRight-click the identified CADImage plugin DLL file and select Properties. In the Details tab, check the File Version field to confirm it shows 12.0.0.5.Affected if The plugin file version is exactly 12.0.0.5
-
Confirm .dwg file association with IrfanViewCheck if .dwg files are associated with IrfanView by right-clicking any .dwg file in Windows Explorer, selecting 'Open with' > 'Choose another app', and seeing if IrfanView is listed, or check IrfanView's settings under 'Options' > 'Properties/Settings' > 'File types' to see if CAD/DWG is enabled.Affected if IrfanView is configured to handle or preview .dwg files
You are affected if IrfanView version 4.50 (64-bit) is installed with the CADImage plugin version 12.0.0.5 and the plugin is enabled to handle .dwg 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 unknown .dwg files in IrfanView until the CADImage plugin is updated to a patched version. If exploitation is suspected, isolate the affected system and scan for indicators of compromise.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15744 — 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-15744 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