CVE-2017-15759
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+0x000000000001b3f3."
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 in the BabaCAD4Image plugin version 1.3 for IrfanView 4.50 (64-bit) allows arbitrary code execution or denial of service via a specially crafted .dwg CAD file. The vulnerability is triggered during file parsing, causing a User Mode Write Access Violation near NULL at the ShowPlugInOptions function.
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.
-
Verify IrfanView versionCheck the IrfanView executable (usually in C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) by right-clicking irfanview.exe, selecting Properties, and viewing the Details tab. Look for version 4.50.Affected if The installed version is exactly 4.50 (64-bit)
-
Locate the BabaCAD4Image plugin fileNavigate to the IrfanView Plugins folder (typically C:\Program Files\IrfanView\Plugins\ or C:\Program Files (x86)\IrfanView\Plugins\) and search for a file named BabaCAD4Image.dll or similar BabaCAD-related DLL.Affected if A BabaCAD4Image plugin DLL file exists in the Plugins folder
-
Verify the plugin versionRight-click the BabaCAD4Image plugin DLL file, select Properties, then the Details tab, and check the File Version or Product Version field.Affected if The plugin version is 1.3
-
Confirm plugin is loadable by IrfanViewOpen IrfanView, go to Menu > Properties/Settings > Plugins. Look for BabaCAD4Image in the list of loaded plugins.Affected if The BabaCAD4Image plugin appears as enabled or loaded in IrfanView's plugin list
A user is affected if they have IrfanView 4.50 (64-bit) with the BabaCAD4Image plugin version 1.3 installed and enabled, and they attempt to open a specially crafted .dwg CAD file.
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 dataRemove or disable the BabaCAD4Image plugin until an official patch is available, and avoid opening untrusted .dwg files.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15759 — 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-15759 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