Security readout for executives and security teams
Plain-English summary
This CVE concerns STDU Viewer 1.6.375 handling a malicious .xps document. Opening a crafted file could let an attacker crash the application or potentially run code. The public record does not confirm real-world exploitation or name a patched version.
Executive priority
Prioritize if STDU Viewer is present in the fleet or XPS files are business-relevant. Otherwise, handle as a targeted legacy application cleanup item with phishing-style document risk.
Technical view
The CVE describes a user-mode write access violation in STDU Viewer 1.6.375 triggered by a crafted XPS file, with impact stated as arbitrary code execution or denial of service. Available sources provide limited root-cause detail, no CVSS score, and no vendor remediation detail.
Likely exposure
Exposure is most likely on endpoints where STDU Viewer 1.6.375 remains installed and users can open untrusted .xps files. This appears to be a legacy desktop-software risk, not a server-side exposure.
Exploitation context
The source material supports a crafted-file attack scenario. CISA KEV status is false in the bundle, and no cited source reports active exploitation. Practical exploitation reliability is not established by the provided evidence.
Researcher notes
The public details are sparse. The advisory identifies the crash condition and claimed impact, but the bundle lacks CVSS, CWE, patch status, exploit maturity, and deeper technical analysis. Avoid assuming affected versions beyond STDU Viewer 1.6.375.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375.
- Remove or replace STDU Viewer where it is not required.
- Restrict untrusted .xps attachments and downloads.
- Check vendor or project guidance for fixed versions.
- Use endpoint controls to limit risky document viewers.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 is installed.
- Review default handlers for .xps files.
- Check email and web controls for .xps filtering.
- Confirm users do not rely on the legacy viewer.
- Document compensating controls if removal is delayed.
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-14572 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-14572CVE 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.