CVE-2017-15783
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 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 CADImage+0x0000000000285ce1."
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 for Windows Version 2.43 contains a memory corruption vulnerability when parsing specially crafted .dwg files. The vulnerability occurs in the CADImage component where data from an invalid memory address controls branch selection, potentially allowing attackers to achieve code execution beyond simple 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.exe in typical installation directories: C:\Program Files\XnView\XnView.exe or C:\Program Files (x86)\XnView\XnView.exe. Use PowerShell command: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)' -Filter 'XnView.exe' -Recurse -ErrorAction SilentlyContinueAffected if XnView.exe is found in either location
-
Verify installed version numberRight-click on the XnView.exe file, select Properties, then check the Version tab for the File Version. Alternatively, run: wmic datafile where "name='C:\\Program Files\\XnView\\XnView.exe'" get VersionAffected if The displayed version is exactly 2.43
-
Confirm CADImage/dwg parsing capability presentCheck for the presence of CAD-related DLLs or modules in the XnView installation folder (such as CADImage.dll or similar components that handle .dwg files). Look in the XnView program directory for files with 'cad' or 'dwg' in the nameAffected if DWG parsing components exist in the XnView installation folder
-
Identify exposure to untrusted .dwg filesReview system or user activity logs, email attachments, or downloaded files for recent .dwg file opens. Check if users have been opening CAD files from unknown or untrusted sourcesAffected if Users have opened or are likely to open specially crafted .dwg files from untrusted sources
You are affected if XnView Classic version 2.43 is installed AND users can open or have opened untrusted .dwg files in this application.
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 unknown .dwg files in XnView Classic. Check for available vendor patches for XnView and apply them. Consider using alternative, more secure CAD viewing software for untrusted files or implement additional input validation at the network perimeter.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15783 — 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-15783 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