CVE-2017-15765
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 is used as one or more arguments in a subsequent Function Call starting at CADIMAGE+0x00000000003e9462."
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 confidenceIrfanView 64-bit version 4.50 with CADImage plugin version 12.0.0.5 suffers from a memory corruption vulnerability when parsing specially crafted .dwg files. The vulnerability involves data from a faulting address being used as arguments in a subsequent function call, indicating a write-what-where or similar memory corruption condition that can lead to denial of service or potentially arbitrary 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.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 64-bit installationLocate i_view64.exe in the IrfanView installation directory (typically C:\Program Files\IrfanView). Right-click the file, select Properties, and verify the File Version is 4.50.Affected if i_view64.exe version 4.50 is present on the system
-
Verify CADImage plugin versionNavigate to the IrfanView Plugins folder (usually C:\Program Files\IrfanView\Plugins). Locate CADImage.dll or CADImage plugin files. Right-click and check Properties > Details for version, or run 'dir CADImage* /s' from the IrfanView directory in Command Prompt.Affected if CADImage plugin version 12.0.0.5 is installed
-
Confirm CADImage plugin is loadedOpen IrfanView, go to Help > About > Plugins. Verify CADImage appears in the list of loaded plugins. Alternatively, attempt to open any .dwg file or view its thumbnail in IrfanView.Affected if CADImage plugin is enabled and listed as loaded in IrfanView
-
Check for .dwg file handling capabilityAttempt to open a .dwg file in IrfanView or check if .dwg file thumbnails render in Windows Explorer using IrfanView. If IrfanView can process .dwg files, the vulnerable code path is reachable.Affected if IrfanView can open or thumbnail .dwg files via the CADImage plugin
User is affected if both IrfanView 64-bit version 4.50 and CADImage plugin version 12.0.0.5 are installed together and the plugin is capable of handling .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 dataUpdate the CADImage plugin to a patched version if available, or disable/remove the CADImage plugin from IrfanView installations until a fix is released. Avoid opening untrusted .dwg files in affected IrfanView configurations.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15765 — 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-15765 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