CVE-2017-15757
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 cause a denial of service or possibly have unspecified other impact via a crafted .dwg file, related to "Data from Faulting Address controls Branch Selection starting at BabaCAD4Image!ShowPlugInOptions+0x00000000000029ba."
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 allows attackers to execute arbitrary code or cause denial of service via a specially crafted .dwg file. The vulnerability involves 'Data from Faulting Address controls Branch Selection,' indicating an attacker can control program flow based on memory contents they control.
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.
-
Check IrfanView versionOpen IrfanView and go to Help > About, or run 'irfanview.exe /about' from command line. Verify the version is 4.50.Affected if The installed IrfanView version equals exactly 4.50
-
Check BabaCAD4Image plugin versionLocate the BabaCAD4Image plugin DLL in the IrfanView plugins directory. Right-click the file, select Properties, and check the File version tab. Alternatively, list all DLLs in the plugins folder and look for files containing 'babacad' in the filename.Affected if The plugin file version is 1.3, or the file BabaCAD4Image.dll version shows 1.3
-
Verify plugin is present in the plugins directoryNavigate to the IrfanView installation directory (commonly C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView). Check for a folder named 'Plugins' and confirm the BabaCAD4Image plugin DLL exists in that folder.Affected if The BabaCAD4Image DLL file exists in the IrfanView plugins folder and would be loaded by IrfanView at startup
-
Confirm .dwg file association or plugin load behaviorOpen IrfanView and attempt to open any .dwg file, or check the plugin loading behavior. The plugin loads automatically when present in the plugins directory. Observe whether IrfanView attempts to process the .dwg file through the BabaCAD4Image plugin.Affected if IrfanView loads the BabaCAD4Image plugin automatically and would process .dwg files through the vulnerable plugin code
You are affected if you have IrfanView version 4.50 with the BabaCAD4Image plugin version 1.3 installed and the plugin is present in the plugins directory, as the vulnerability triggers when opening 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 dataUpdate the BabaCAD4Image plugin to the latest version if available, or remove/disable the plugin until a patch is released. Avoid opening untrusted .dwg files in IrfanView with this plugin enabled.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15757 — 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-15757 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