Security readout for executives and security teams
Plain-English summary
CVE-2017-14289 is a file-parsing vulnerability in STDU Viewer 1.6.375. A malicious .jb2 file can reportedly crash the application or execute arbitrary code. Business risk is concentrated on endpoints where this viewer is installed and users may open files from email, downloads, or external parties.
Executive priority
Prioritize this as a targeted endpoint exposure issue, not an internet-facing emergency based on supplied evidence. Act quickly if STDU Viewer is deployed broadly or used to open external document files.
Technical view
The CVE describes a crafted JBIG2 .jb2 file causing a user-mode write access violation in STDUJBIG2File near DllGetClassObject. The reported impact is arbitrary code execution or denial of service. The source bundle does not provide CVSS, CWE, confirmed fixed versions, or detailed vendor remediation.
Likely exposure
Exposure is likely limited to systems running STDU Viewer 1.6.375 that can receive and open untrusted .jb2 files. The supplied CPE and affected-product metadata are incomplete, so inventory confirmation is necessary.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation appears file-based and would depend on a user or workflow opening a crafted .jb2 file in the vulnerable viewer.
Researcher notes
The public metadata is thin: no CVSS, CWE, CPE, patch statement, or KEV signal is supplied. Analysis should stay anchored to STDU Viewer 1.6.375 and crafted .jb2 handling unless additional vendor or exploit-intelligence sources are reviewed.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375 installations.
- Check vendor or trusted software-maintainer guidance for fixed or replacement versions.
- Restrict opening untrusted .jb2 files in STDU Viewer.
- Remove STDU Viewer where there is no business need.
- Use email and web filtering to reduce delivery of unexpected .jb2 files.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 exists in endpoint software inventory.
- Review file association policies for .jb2 and JBIG2 documents.
- Check security controls for handling unexpected .jb2 attachments or downloads.
- Verify remediation decisions against vendor-confirmed guidance, not assumed fixed versions.
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-14289 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-14289CVE 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.