CVE-2017-15773
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+0x0000000000285d79."
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 Version 2.43 contains a memory corruption vulnerability when parsing specially crafted DWG CAD files. The vulnerability manifests as a read access violation in the CADImage component, indicating an out-of-bounds memory read or improper bounds checking during DWG file parsing. Attackers can trigger this by tricking users into opening a malicious DWG file, causing application crash (DoS) or potentially achieving code execution.
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 XnView installation and versionCheck the program's version by opening XnView, going to Help > About, or right-clicking the executable and viewing Properties > Details. Look for the version number in the 'File version' or 'Product version' field.Affected if The installed version is exactly 2.43 or falls within the 2.43 release line.
-
Locate the CADImage componentSearch the XnView installation directory (commonly C:\Program Files\XnView or C:\Program Files (x86)\XnView) for files named CADImage.dll, cadimage.dll, or similar CAD-related DLL files.Affected if The CADImage component DLL is present in the XnView installation directory.
-
Verify DWG file handling capabilityCheck if XnView has DWG support enabled by going to Options > File Formats or examining the formats\cad subfolder within the XnView directory. Look for DWG listed among supported read formats.Affected if DWG format support is enabled or the CAD format plugin is loaded.
-
Check for recently opened DWG filesReview the XnView history or recently opened files list (Options > General > History), or examine the application's recent documents for any .dwg file entries.Affected if Users have opened or attempted to open DWG files using this XnView installation.
A user is affected if XnView Classic version 2.43 is installed with the CADImage component and DWG file support is enabled, allowing users to open potentially malicious DWG files.
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 to a patched version of XnView if available; otherwise implement file type restrictions or input validation to block untrusted DWG files, and consider alternative viewing solutions until a fix is released.
- 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-15773 — 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-15773 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