Security readout for executives and security teams
Plain-English summary
A malicious .jb2 document could crash STDU Viewer 1.6.375 or potentially run attacker-controlled code when a user opens it. The business risk is mainly endpoint compromise through unsafe document handling, but the public record provided is sparse and does not name a patch.
Executive priority
Prioritize if STDU Viewer 1.6.375 exists on user workstations or document-processing systems. If absent, track as low operational concern. If present, reduce exposure quickly because arbitrary code execution is possible and no patch is identified in the provided sources.
Technical view
CVE-2017-14690 describes arbitrary code execution or denial of service in STDU Viewer 1.6.375 via a crafted .jb2 file. The CVE notes that data from the faulting address can control a subsequent write address in STDUJBIG2File, indicating a memory-corruption condition.
Likely exposure
Exposure is likely limited to systems with STDU Viewer 1.6.375 installed, especially where users can receive or open untrusted .jb2/JBIG2 files.
Exploitation context
The provided sources do not show CISA KEV listing, active exploitation, public weaponization status, CVSS, CWE, or confirmed vendor remediation. Treat exploitation status as unknown.
Researcher notes
The evidence base is minimal: the CVE description and linked advisory identify STDU Viewer 1.6.375 and a crafted .jb2 trigger, but do not provide CVSS, CWE, affected CPEs, exploit prevalence, or fixed versions. Avoid assuming impact beyond this version and file type.
Mitigation direction
- Inventory and remove STDU Viewer 1.6.375 where it is not required.
- Check vendor or trusted advisory sources for upgrade or replacement guidance.
- Block or quarantine untrusted .jb2 files at email and web gateways.
- Restrict .jb2 file association to approved, maintained viewers.
- Open legacy document formats only in isolated environments.
Validation and detection
- Search endpoint software inventory for STDU Viewer 1.6.375.
- Review file associations for .jb2 and JBIG2 content.
- Check whether users regularly receive or process .jb2 files.
- Look for crash telemetry involving STDUJBIG2File or STDU Viewer.
- Confirm any remediation against vendor guidance before closure.
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-14690 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-14690CVE 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.