CVE-2017-15754
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 BabaCAD4Image plugin version 1.3 allows attackers to execute arbitrary code or cause a denial of service via a crafted .dwg file, related to a "User Mode Write AV near NULL starting at BabaCAD4Image!ShowPlugInOptions+0x0000000000013968."
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 confidenceThe BabaCAD4Image plugin version 1.3 for IrfanView 4.50 64-bit contains a memory corruption vulnerability when parsing specially crafted .dwg files. The vulnerability triggers a User Mode Write Access Violation near NULL at a specific offset within the ShowPlugInOptions function, allowing attackers to potentially execute arbitrary code or cause 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= 1.3CVSS 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.
-
Locate IrfanView 4.50 installationSearch for irfanview.exe and check its version property, or query the Windows registry under HKLM\SOFTWARE\IrfanView for InstallPath and verify the version equals 4.50Affected if IrfanView version 4.50 is installed on the system
-
Find the BabaCAD4Image plugin fileBrowse the IrfanView installation directory for a Plugins folder, and locate a DLL file associated with BabaCAD4Image (commonly named BabaCAD4Image.dll or similar). Right-click the file and view Properties > Details to confirm the version is 1.3Affected if The BabaCAD4Image plugin DLL version 1.3 is present in the IrfanView plugins directory
-
Confirm the plugin is loaded by IrfanViewOpen IrfanView, go to menu Options > Properties/Settings > Plugins, and verify that the BabaCAD4Image plugin appears in the list and is checked or enabledAffected if The BabaCAD4Image plugin is listed as loaded or enabled in IrfanView's plugin configuration
-
Check for .dwg file associations or preview capabilityIn IrfanView, attempt to open a .dwg file or check the file type list in Options > Properties/Settings > File Types to see if .dwg is registered as a supported formatAffected if IrfanView can process or preview .dwg files, indicating the vulnerable code path can be triggered
You are affected if IrfanView 4.50 is installed with the BabaCAD4Image plugin version 1.3 enabled and capable of opening .dwg files, allowing the memory corruption to trigger when a specially crafted .dwg file is processed.
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 dataIf an updated version of the BabaCAD4Image plugin is available from the vendor, apply the patch. Otherwise, disable or remove the BabaCAD4Image plugin from IrfanView installations until a fix is released, and restrict acceptance of .dwg files from untrusted sources.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15754 — 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-15754 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