CVE-2017-15752
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 "Data from Faulting Address controls subsequent Write Address starting at BabaCAD4Image!ShowPlugInOptions+0x000000000004d6b0."
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 confidenceA memory corruption vulnerability in the BabaCAD4Image plugin version 1.3 for IrfanView 64-bit versions 4.50 and above allows attackers to achieve arbitrary code execution or cause denial of service by parsing a specially crafted .dwg CAD file. The vulnerability involves a write-what-where condition where data from a faulting address controls a subsequent write address.
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.
-
Identify IrfanView installation and versionOpen IrfanView and go to Help > About, or right-click the IrfanView executable and select Properties > Details to view the version numberAffected if The version shown is 4.50 or higher on a 64-bit Windows system
-
Locate and verify BabaCAD4Image pluginNavigate to the IrfanView plugins directory (typically named 'plugins' or 'plugins64' in the installation folder) and search for a file named BabaCAD4Image or similar CAD-related plugin file. Check the file properties or metadata for the versionAffected if The BabaCAD4Image plugin version 1.3 is present in the plugins directory
-
Confirm plugin is loaded and activeIn IrfanView, go to Options > Properties/Settings > Plugins to view the list of loaded plugins, or attempt to open a .dwd file to see if IrfanView attempts to process itAffected if The BabaCAD4Image plugin appears in the loaded plugins list or IrfanView attempts to open .dwg files using it
-
Check for recent .dwg file activityReview the system for recently opened .dwg files, or check IrfanView's recently opened files list if availableAffected if Recent .dwg files were opened using IrfanView with the vulnerable plugin enabled
A user is affected if they have IrfanView 64-bit version 4.50 or higher with the BabaCAD4Image plugin version 1.3 installed and enabled, and they open or have opened untrusted .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 or unverified .dwg files in IrfanView until an updated plugin version is available. Consider removing or disabling the BabaCAD4Image plugin if not required, and monitor for security updates from the plugin vendor.
- 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-15752 — 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-15752 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