CVE-2017-14565
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 cause a denial of service or possibly have unspecified other impact via a crafted .xps file, related to a "Possible Stack Corruption starting at Unknown Symbol @ 0x00000000038f2fbf called from image00000000_00400000+0x0000000000240065."
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 confidenceStack corruption vulnerability in STDU Viewer 1.6.375 when parsing specially crafted XPS files. The vulnerability occurs during XPS document parsing, causing corruption of the stack that can lead to denial of service or potentially allow arbitrary code execution. The crash occurs at a specific memory address indicating the corruption originates from image parsing logic.
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.
-
Verify STDU Viewer installationSearch for STDU Viewer executable (stdview.exe or stduviewer.exe) in common program directories: C:\Program Files\, C:\Program Files (x86)\, or use 'where stdview.exe' or 'where stduviewer.exe' from command promptAffected if STDU Viewer executable is found on the system
-
Confirm installed versionRight-click the STDU Viewer executable, select Properties, then look at the Version tab for the File Version. Alternatively, run 'stdview.exe /?' or check Add/Remove Programs for the versionAffected if Version is exactly 1.6.375
-
Check for XPS file handling capabilitySTDU Viewer natively supports XPS format; verify by attempting to open an XPS file or checking file associations for .xps files pointing to STDU Viewer using 'assoc .xps' or checking registry under HKCR\.xpsAffected if STDU Viewer is associated as the handler for .xps files or has been used to open XPS documents
-
Look for crash artifactsCheck Windows Event Viewer under Windows Logs > Application for crash events related to stdview.exe/stduviewer.exe, or check for dump files in %LOCALAPPDATA%\CrashDumps or application log directoriesAffected if Recent crash events or dump files exist for STDU Viewer involving XPS file processing
System is affected if STDU Viewer version 1.6.375 is installed and has been used to open or is associated with handling XPS files, as the stack corruption occurs specifically during XPS document parsing in this exact version.
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 unverified XPS files with STDU Viewer. If available, update to a patched version from the vendor. Consider running the application in a sandboxed environment or using alternative document viewers to mitigate potential impact until a fix is applied.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14565 — 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-14565 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