IrfanviewApplication

CVE-2017-15738

HIGH · 7.8 CVSS v3.0 Published 2017-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
IrfanView 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+0x00000000003d22d8."

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 confidence

A memory corruption vulnerability in IrfanView's CADImage plugin version 12.0.0.5 allows attackers to cause a denial of service via a specially crafted .dwg file. The vulnerability manifests as a read access violation at a specific memory offset within the CADIMAGE component.

MitigationAvoid opening untrusted or unverified .dwg files in IrfanView with the CADImage plugin; consider disabling the CADImage plugin until an official vendor patch is available.

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
IrfanviewApplication
Affected:= 4.50
CadimageApplication
Affected:= 12.0.0.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check IrfanView installation version
    Locate the IrfanView installation directory (commonly C:\Program Files\IrfanView\ or C:\Program Files (x86)\IrfanView\) and check the version of i_view32.exe or irfanview.exe by right-clicking the file, selecting Properties, and viewing the Version tab. Alternatively, run IrfanView and go to Help > About IrfanView to display the installed version number.
    Affected if The installed IrfanView version is exactly 4.50
  2. Locate and verify CADImage plugin presence
    Navigate to the IrfanView installation directory and look for the CADImage plugin file, typically named CADImage.ifx, CADImage.dll, or similar in a Plugins subfolder. The plugin file should be present in the Plugins directory for the vulnerability to be exploitable.
    Affected if The CADImage plugin file exists in the IrfanView Plugins folder
  3. Check CADImage plugin version
    Right-click the CADImage plugin file (CADImage.ifx or CADImage.dll) in the Plugins folder, select Properties, and examine the Version tab to determine the exact plugin version. Alternatively, check any version information file or manifest bundled with the plugin.
    Affected if The CADImage plugin version is exactly 12.0.0.5
  4. Confirm plugin can process DWG files
    Open IrfanView and attempt to open a .dwg file, or verify that DWG file type associations are present in IrfanView's configuration. The vulnerability only applies when the CADImage plugin is loaded and capable of processing DWG files.
    Affected if DWG file support is enabled and the CADImage plugin is loaded by IrfanView when viewing DWG files

A user is affected if they have IrfanView version 4.50 with CADImage plugin version 12.0.0.5 installed and the plugin is capable of loading DWG files, as this specific version combination contains the memory corruption flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening untrusted or unverified .dwg files in IrfanView with the CADImage plugin; consider disabling the CADImage plugin until an official vendor patch is available.

Fix this in Irfanview Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15738 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-15738 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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