CVE-2017-15781
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 "Read Access Violation on Control Flow starting at CADImage+0x0000000000286a76."
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 confidenceXnView Classic 2.43 contains a memory corruption vulnerability in its CADImage library when parsing malformed .dwg (CAD) files. The vulnerability manifests as a read access violation on control flow (CADImage+0x0000000000286a76), allowing attackers to potentially achieve arbitrary code execution or cause a denial of service via a specially crafted .dwg file.
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.
-
Verify XnView Classic installationCheck if XnView Classic is installed on the system. Common installation paths include C:\Program Files\XnView\ or C:\Program Files (x86)\XnView\. On Linux, check /opt/xnview or ~/.local/share/xnview.Affected if XnView Classic is not installed on the system
-
Confirm installed version is 2.43Launch XnView Classic and navigate to Help > About, or right-click the executable and view Properties > Details to see the version number. Compare this to the affected version 2.43.Affected if The installed version is exactly 2.43
-
Identify if CADImage library is presentCheck for the CADImage library file within the XnView installation directory. This is typically named CadImage.dll or similar CAD-related DLL that handles .dwg file parsing.Affected if The CADImage library (CadImage.dll) is present in the XnView installation directory
-
Determine if users process .dwg files with XnViewReview file association settings and user workflows to determine if .dwg files are being opened or previewed using XnView Classic. Check email gateways, file shares, or user行为 for .dwg file processing.Affected if Users routinely open or preview .dwg files using XnView Classic 2.43
A system is affected if XnView Classic version 2.43 is installed and users open or preview maliciously crafted .dwg files with the built-in CADImage library.
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 XnView Classic until a vendor patch is available; implement file type screening and antivirus scanning at email gateways and file shares to block or quarantine .dwg files from unknown sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15781 — 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-15781 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