CVE-2017-15760
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+0x000000000001ce82."
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 CAD files. The bug manifests as a user-mode write access violation occurring near a NULL address at ShowPlugInOptions, indicating improper bounds checking or buffer handling during DWG file parsing that can be exploited for arbitrary code execution or 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.
-
Verify IrfanView versionCheck if IrfanView version 4.50 is installed. Look in the program files directory for IrfanView (usually C:\Program Files\IrfanView\i_view64.exe or C:\Program Files (x86)\IrfanView\i_view32.exe) and view the file properties to confirm version 4.50, or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IrfanView\Version or HKEY_CURRENT_USER\Software\IrfanView for the installed version.Affected if IrfanView version 4.50 is installed
-
Locate BabaCAD4Image pluginCheck for the presence of the BabaCAD4Image plugin DLL in the IrfanView plugins directory. The plugin is typically located in C:\Program Files\IrfanView\Plugins\ or C:\Program Files (x86)\IrfanView\Plugins\ and should appear as Babacad4image.dll or similar naming convention. Check the file properties to confirm version 1.3.Affected if BabaCAD4Image plugin version 1.3 exists in the IrfanView plugins folder
-
Confirm plugin is loadedOpen IrfanView and navigate to Options > Properties/Settings > Plugins to see if the BabaCAD4Image plugin is listed as loaded and enabled. Alternatively, attempt to open a .dwg file via File > Open to see if IrfanView attempts to use the plugin.Affected if The BabaCAD4Image plugin appears enabled in the IrfanView plugins list or attempts to process .dwg files
A user is affected if they have IrfanView 4.50 installed with the BabaCAD4Image plugin version 1.3 present and enabled, and they open a specially crafted .dwg 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 dataAvoid opening untrusted or unverified .dwg files with the BabaCAD4Image plugin; disable or remove the plugin if no update is available from the vendor; consider using alternative CAD viewers for untrusted files.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15760 — 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-15760 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