CVE-2017-14568
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 · uneditedSTDU Viewer 1.6.375 allows attackers to execute arbitrary code or cause a denial of service via a crafted .xps file, related to an "Illegal Instruction Violation starting at Unknown Symbol @ 0x000000000297024c called from STDUXPSFile!DllUnregisterServer+0x0000000000025630."
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 confidenceSTDU Viewer 1.6.375 contains a memory corruption vulnerability in its XPS file parsing module (STDUXPSFile.dll). A crafted .xps file with malformed content triggers an illegal instruction violation, which can be leveraged for arbitrary code execution or causes denial of service via application crash.
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= 1.6.375CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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.
-
Locate STDU Viewer installation directorySearch for 'STDU Viewer.exe' in Program Files folders or use 'dir /s /b C:\"STDU Viewer.exe"' from an elevated command promptAffected if The executable exists on the system, indicating STDU Viewer is installed
-
Identify installed versionRight-click STDU Viewer.exe, select Properties, then view the Details tab for Product Version. Alternatively, run 'wmic product where "name like 'STDU%' get name,version' from command promptAffected if Version is 1.6.375, matching the affected version listed in the CVE
-
Verify vulnerable XPS parsing module existsCheck for STDUXPSFile.dll in the same directory as STDU Viewer.exe (typically in Program Files or Program Files (x86) under the STDU Viewer folder)Affected if STDUXPSFile.dll is present, indicating the vulnerable XPS parsing component is installed
-
Confirm XPS file association or recent usageOpen Windows Registry Editor and check HKEY_CLASSES_ROOT\.xps for file association, or check recent file history in %APPDATA%\STDUViewer for recently opened .xps filesAffected if XPS file association is set to STDU Viewer or recent .xps files have been opened with the application
A system is affected if STDU Viewer version 1.6.375 is installed with the STDUXPSFile.dll module present and XPS file handling is enabled or has been used.
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 dataDo not open untrusted or unverified .xps files in STDU Viewer. Until an official vendor patch is available, implement compensating controls such as restricting file type associations, using alternative document viewers, or deploying endpoint detection tools to monitor for exploitation attempts.
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14568 — 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-14568 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