CVE-2017-15788
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 · uneditedXnView Classic for Windows Version 2.43 allows attackers to execute arbitrary code or cause a denial of service via a crafted .dwg file, related to a "User Mode Write AV starting at CADImage+0x0000000000002d83."
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 confidenceXnView Classic Version 2.43 contains a memory corruption vulnerability when parsing specially crafted .dwg files, triggering a user-mode write access violation at CADImage+0x0002d83. This can potentially allow arbitrary code execution or cause application 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= 2.43CVSS 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 XnView Classic installationCheck for XnView Classic executable (xnview.exe) in common installation directories such as C:\Program Files\XnView\ or C:\Program Files (x86)\XnView\. Use File Explorer or command: dir /s C:\xnview.exeAffected if XnView Classic is installed on the system
-
Identify installed versionRight-click xnview.exe, select Properties, then view the Details tab for Product Version. Alternatively, run: xnview.exe /? or check Help > About in the applicationAffected if Version displayed is exactly 2.43
-
Verify DWG file handling capabilityOpen XnView Classic and attempt to preview a .dwg file, or check File > Open with .dwg extension visible in the file dialog. XnView uses the CADImage plugin (cadimage.dll) to handle DWG filesAffected if XnView can open or preview .dwg files and the CADImage component is active
-
Check for malicious DWG exposureReview recent or scheduled files opened in XnView, particularly from untrusted sources. Examine file location history or recent documents accessed via XnViewAffected if Any .dwg file from an untrusted or unknown source has been opened in XnView version 2.43
System is affected if XnView Classic version 2.43 is installed and is capable of opening or previewing .dwg files, as the vulnerability triggers during DWG parsing.
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 XnView Classic to a patched version if available; otherwise, avoid opening untrusted .dwg files in XnView until a fix is released.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15788 — 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-15788 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