Security readout for executives and security teams
Plain-English summary
CVE-2017-14290 is a file-parsing flaw in STDU Viewer 1.6.375. A malicious .jb2 file could crash the viewer or potentially run attacker-controlled code when opened. The provided sources do not include a CVSS score, vendor fix, or evidence of active exploitation.
Executive priority
Prioritize removal or containment if STDU Viewer 1.6.375 exists in the environment. Business urgency is lower if the application is absent, but legacy document viewers are difficult to defend when handling untrusted files.
Technical view
The CVE describes heap corruption in STDU Viewer 1.6.375 when processing a crafted JB2 file. Reported impact is arbitrary code execution or denial of service. The public metadata lacks CVSS, CWE, reliable CPEs, patch information, and detailed affected-product normalization.
Likely exposure
Exposure is most likely on Windows endpoints where STDU Viewer 1.6.375 is installed and users can open untrusted .jb2 files. The source bundle does not prove exposure for other STDU versions or products.
Exploitation context
The provided bundle lists a public advisory reference, but KEV is false and no cited source states active exploitation. Treat this as a malicious-file risk requiring user interaction unless additional vendor guidance says otherwise.
Researcher notes
Key gaps are material: no CVSS, CWE, CPE, vendor fix, or active exploitation evidence in the bundle. The strongest technical signal is heap corruption tied to crafted .jb2 parsing and reported arbitrary code execution or denial of service.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375.
- Check vendor or maintainer guidance for fixed versions or retirement advice.
- Remove STDU Viewer where it is not business-required.
- Restrict opening untrusted .jb2 files from email, web, and shared drives.
- Use endpoint controls to limit legacy document viewers.
Validation and detection
- Confirm installed STDU Viewer versions from software inventory.
- Review file associations for .jb2 and related JB2 document handling.
- Search security telemetry for crashes involving STDU Viewer and JB2 files.
- Check whether users receive or process .jb2 files from external sources.
- Track vendor advisories for any patch or workaround details.
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-14290 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-14290CVE 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.