CVE-2017-15755
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 verifier!AVrfpDphFindBusyMemoryNoCheck+0x0000000000000091."
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 confidenceIrfanView 64-bit version 4.50 with the BabaCAD4Image plugin version 1.3 suffers from a memory corruption vulnerability when parsing specially crafted .dwg files. The issue manifests as 'Data from Faulting Address controls Branch Selection,' indicating a write-what-where or similar memory corruption condition that can lead to denial of service or potentially arbitrary code execution.
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.
-
Confirm IrfanView 64-bit installationCheck for IrfanView 64-bit in Program Files (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) or use system inventory tools to detect the installed softwareAffected if IrfanView 64-bit version 4.50 is installed
-
Verify IrfanView versionOpen IrfanView, go to Help > About, or check the version property of irfanview.exe in the installation directoryAffected if Version displayed is exactly 4.50
-
Detect BabaCAD4Image plugin presenceCheck the IrfanView plugins folder (typically [InstallDir]\plugins\) for BabaCAD4Image.dll or babaCAD4Image.* files; alternatively, in IrfanView go to Properties > Plugins to list loaded pluginsAffected if BabaCAD4Image plugin is present in the plugins directory or listed in IrfanView's plugin list
-
Confirm plugin version is 1.3Right-click the BabaCAD4Image.dll file, select Properties, and check the File Version tab; or check version info through command line tools like powershell (Get-Item).VersionInfoAffected if The plugin file shows version 1.3
-
Check .dwg file association or supportIn IrfanView, attempt to open a .dwg file or check File > Open dialog for .dwg extension visibility; also check if the plugin handles .dwg in IrfanView's plugin informationAffected if IrfanView can load or preview .dwg files through the BabaCAD4Image plugin
A user is affected if they have IrfanView 64-bit version 4.50 with BabaCAD4Image plugin version 1.3 installed and .dwg file support is enabled in the plugin.
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 or remove the BabaCAD4Image plugin from IrfanView installations; alternatively, upgrade to a patched version of IrfanView that addresses this vulnerability in the plugin or remove support for .dwg file handling if not required.
- 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-15755 — 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-15755 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