Security readout for executives and security teams
Plain-English summary
This CVE concerns STDU Viewer 1.6.375 crashing or potentially suffering unspecified impact when a user opens a malicious DjVu file. The public record does not provide CVSS scoring, confirmed exploitation, or a named fix. Business urgency depends on whether this legacy viewer is installed and used to open untrusted documents.
Executive priority
Treat this as a targeted legacy-software exposure check, not an emergency based on current evidence. Prioritize remediation if STDU Viewer 1.6.375 is deployed in document-heavy or externally facing workflows.
Technical view
The issue is triggered by a crafted .djvu file in STDU Viewer 1.6.375. The CVE text links the behavior to faulting address data being reused as function-call arguments in STDUDjVuFile. Public metadata does not identify a CWE, CPE, reliable impact beyond denial of service, or remediation version.
Likely exposure
Exposure is most plausible on Windows endpoints where STDU Viewer 1.6.375 is installed and associated with DjVu documents, especially users receiving files from email, web downloads, or archives. The CVE metadata does not provide complete affected-product identifiers.
Exploitation context
The sources describe a crafted-file condition, so exploitation appears to require a target user or workflow to open a malicious .djvu file. There is no KEV listing and no cited source in the bundle confirming active exploitation.
Researcher notes
Evidence is sparse. The CVE description names STDU Viewer 1.6.375 and a crafted DjVu trigger, but NVD-style severity, CWE, CPE, exploit maturity, and fix details are absent from the provided bundle.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375 installations.
- Check vendor or advisory guidance for any fixed or safer version.
- Remove the viewer where DjVu support is not business-required.
- Block or quarantine untrusted .djvu attachments where practical.
- Prefer supported document viewers with maintained security updates.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 exists in software inventory.
- Check file associations for .djvu on managed endpoints.
- Review endpoint telemetry for STDU Viewer crashes after DjVu opens.
- Verify document intake workflows do not require untrusted DjVu handling.
- Record compensating controls if no vendor fix is 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-14689 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-14689CVE 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.