Security readout for executives and security teams
Plain-English summary
A vulnerable STDU Viewer version can crash or potentially run attacker-controlled code when handling a specially crafted XPS document. The source bundle does not provide a CVSS score, fixed version, or evidence of active exploitation.
Executive priority
Treat this as a targeted endpoint risk, not a confirmed emergency. Prioritize remediation where STDU Viewer is still installed on user workstations or handles externally supplied documents.
Technical view
CVE-2017-14570 affects STDU Viewer 1.6.375 through crafted .xps file handling, described as arbitrary code execution or denial of service. The CVE references a user-mode write access violation near NULL in wow64 initialization context, but public details are limited.
Likely exposure
Exposure is likely limited to endpoints with STDU Viewer 1.6.375 installed, especially where users can open XPS files from external or untrusted sources.
Exploitation context
The bundle does not list CISA KEV status or active exploitation evidence. Exploitation would require the vulnerable viewer to process a malicious XPS file, based on the CVE description.
Researcher notes
Public evidence is sparse: no CVSS, CWE, patch information, or exploit-in-the-wild signal is provided. Analysis should stay focused on STDU Viewer 1.6.375 and crafted XPS handling unless additional vendor data is obtained.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375.
- Check STDU Viewer guidance for updates or replacement options.
- Remove STDU Viewer where it is not business-required.
- Restrict opening untrusted XPS files in vulnerable environments.
- Use application control for obsolete document viewers.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 is installed.
- Review XPS file associations on managed endpoints.
- Check whether users require STDU Viewer for business workflows.
- Confirm endpoint controls cover legacy document viewers.
- Review crash telemetry involving STDU Viewer and XPS files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-14570 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wlinzi/security_advisories/tree/master/CVE-2017-14570CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.