CVE-2017-15742
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 a "Read Access Violation starting at CADIMAGE+0x00000000003d2328."
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 confidenceA memory corruption vulnerability exists in IrfanView's CADImage plugin (v12.0.0.5) when processing malformed DWG files. The flaw manifests as a read access violation at a specific memory offset in the CADIMAGE component, leading to denial of service and potential code execution. Attackers exploit this by tricking users into opening specially crafted DWG files.
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 IrfanView installation directory (commonly C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) and check the version. In the IrfanView window, go to Help > About IrfanView or look for a file named i_view32.exe and check its version properties.Affected if IrfanView version is exactly 4.50
-
Locate CADImage pluginCheck for CADImage plugin files in the IrfanView plugins directory (typically ...\IrfanView\Plugins\). Look for files named CADImage.dll, cadimage.dll, or similar CAD-related DLLs.Affected if CADImage plugin DLL exists in the plugins folder
-
Verify CADImage plugin versionRight-click the CADImage DLL file, select Properties, and check the File Version tab. The affected version is 12.0.0.5.Affected if CADImage plugin version is exactly 12.0.0.5
-
Check for DWG file associationVerify if IrfanView is associated with or can open .DWG files. Attempt to open a DWG file in IrfanView or check file associations in the system.Affected if IrfanView is configured to open DWG files using the CADImage plugin
User is affected if both IrfanView version 4.50 and CADImage plugin version 12.0.0.5 are installed, and the plugin is available for processing 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 DWG files in vulnerable IrfanView installations. Update or replace the CADImage plugin if a patched version is available, or consider using alternative CAD viewing software until a fix is released.
- Consultation4.0 h
- Implementation3.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 $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15742 — 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-15742 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