CVE-2017-15778
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 a "Read Access Violation starting at CADImage+0x0000000000285de7."
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 read access violation vulnerability when parsing malformed .dwg CAD files. The vulnerability occurs in the CADImage component during file parsing, indicating improper bounds checking that leads to memory corruption capable of causing denial of service or potentially enabling further exploitation.
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 installation by looking for the executable. On Windows, typical paths include C:\Program Files\XnView\xnview.exe or C:\Program Files (x86)\XnView\xnview.exe. Use 'where xnview.exe' or check the Add/Remove Programs list.Affected if XnView Classic is installed on the system
-
Identify installed XnView versionRight-click xnview.exe, select Properties, then look at the Details tab for the Version field. Alternatively, run 'xnview.exe /?' or check the About section within the application.Affected if The version listed is exactly 2.43
-
Verify CADImage component presenceCheck for the CADImage plugin or component within the XnView installation directory. Look for files named cadimage.*, dwg.*, or related CAD processing DLLs in the Plugins or Modules subfolder.Affected if CADImage component or CAD-related plugins are present in the XnView installation directory
-
Confirm .dwg file handling capabilityCheck if .dwg file associations are enabled or if XnView is configured to handle DWG files. Look at Tools > Options > File Associations in XnView, or check system file type associations for .dwg files.Affected if XnView is associated with or configured to open .dwg files
A system is affected if XnView Classic version 2.43 is installed with the CADImage component present and .dwg file handling enabled, allowing malformed .dwg files to trigger the memory read access violation during 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 the latest patched version; avoid opening untrusted or malformed .dwg files until the update is applied.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15778 — 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-15778 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