CVE-2017-15782
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+0x00000000000032eb."
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 v2.43 contains a memory corruption vulnerability when parsing crafted .dwg files. The 'User Mode Write AV' at CADImage+0x32eb indicates a write access violation, likely caused by insufficient bounds checking during DWG parsing that could be exploited for arbitrary code execution or crash the application.
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.
-
Identify installed XnView Classic versionOpen XnView, go to Help > About, or right-click XnView.exe in the installation folder and select Properties > Details to view the File VersionAffected if The version listed is exactly 2.43
-
Locate the XnView executable and confirm version via command lineRun 'wmic datafile where "name like '%xnview%'" get name,version' or check the executable properties in Program FilesAffected if The executable version shows 2.43 exactly
-
Verify .dwg file association or handling capabilityCheck if .dwg files are associated with XnView by opening a .dwg file in XnView, or check Windows registry under HKCR\.dwg to see if XnView is the default handlerAffected if XnView is configured to open .dwg files or has opened .dwg files previously
-
Check for recent .dwg file processing activityReview Windows Event Viewer for recent file access events involving .dwg files, or check browser/download history if .dwg files were downloaded and opened with XnViewAffected if There is evidence that XnView has been used to open .dwg files, especially from untrusted sources
A user is affected if XnView Classic version 2.43 is installed AND the application is used to open or preview .dwg files, which triggers the vulnerable DWG parsing code path.
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. Check for and apply any available security patches from XnView, or consider removing XnView if patches are unavailable and the risk is unacceptable.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15782 — 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-15782 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