Security readout for executives and security teams
Plain-English summary
CVE-2017-8387 concerns STDU Viewer 1.6.375. A victim may need to open an untrusted crafted file and perform specific viewer commands before code execution becomes possible. The supplied sources do not provide a CVSS score, vendor fix, or evidence of active exploitation.
Executive priority
Handle this as a legacy desktop software risk, not an emergency KEV response. Prioritize systems used by staff who process external documents. Because fix information is absent from the supplied sources, removal or vendor guidance is the cleanest path.
Technical view
The CVE describes a user-assisted code execution condition in STDU Viewer 1.6.375 triggered through a crafted file and several user-defined commands, including Ctrl-+ commands. The public record does not identify root cause, CWE, affected CPEs, exploit maturity, or patch status.
Likely exposure
Exposure is most likely on endpoints where STDU Viewer 1.6.375 is installed and users open files from email, downloads, shared drives, or other untrusted sources. The source data does not identify server-side exposure.
Exploitation context
This is not listed in KEV, and the supplied sources do not show active exploitation. The described threat model is user-assisted: an attacker must get a crafted file to a victim and rely on specific user interaction inside STDU Viewer.
Researcher notes
Evidence is thin. The CVE and referenced advisory identify STDU Viewer 1.6.375 and a crafted-file, user-assisted code execution scenario, but omit crash details, root cause, reliable affected-version range, and remediation status. Avoid assuming broader product impact.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375 installations.
- Remove STDU Viewer where it is no longer required.
- Check vendor or advisory guidance for any supported fixed release.
- Restrict opening untrusted files in STDU Viewer.
- Use endpoint controls to limit risky document viewer child processes.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 exists in software inventory.
- Review endpoint telemetry for STDU Viewer opening files from untrusted locations.
- Check whether STDU Viewer is associated with externally received document types.
- Verify users handling external files have safer supported viewers available.
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.
CVE-2017-8387 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-8387CVE 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.