CVE-2017-14561
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 @ 0x00000000048c024d called from STDUXPSFile!DllUnregisterServer+0x0000000000025638."
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 confidenceSTDU Viewer 1.6.375 contains a vulnerability in its XPS file parsing component (STDUXPSFile.dll) where processing a specially crafted .xps file triggers an illegal instruction violation. This can lead to arbitrary code execution or denial of service, as the vulnerability occurs in the DllUnregisterServer function during file processing.
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.
-
Check STDU Viewer installationLook for STDU Viewer in installed programs list (Windows Add/Remove Programs, Programs and Features, or check the installation directory typically under Program Files or Program Files (x86)).Affected if STDU Viewer version 1.6.375 is installed and the STDUXPSFile.dll component is present.
-
Verify STDU Viewer versionRight-click the STDU Viewer executable (commonly named STDUV.exe), select Properties, and check the File Version on the Details tab. Alternatively, open STDU Viewer and look in Help > About.Affected if The installed version is exactly 1.6.375.
-
Confirm vulnerable component existsSearch for STDUXPSFile.dll in the STDU Viewer installation directory (typically in the application folder where STDUV.exe is located).Affected if STDUXPSFile.dll exists in the STDU Viewer installation folder.
-
Check XPS file associationAttempt to open any .xps file with STDU Viewer, or check if .xps file type is associated with STDU Viewer (Right-click an XPS file > Open with > Choose default program).Affected if STDU Viewer is configured to handle or open .xps files.
A user is affected if STDU Viewer version 1.6.375 is installed with STDUXPSFile.dll present and the application can open .xps 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 dataAvoid opening untrusted or unsolicited .xps files in STDU Viewer. If available, apply vendor patches to update STDU Viewer to a fixed version. Consider using application whitelisting or sandboxing to limit exposure to this vulnerability.
- 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-14561 — 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-14561 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