Security readout for executives and security teams
Plain-English summary
CVE-2017-14295 is a file-parsing issue in STDU Viewer 1.6.375. A malicious .jb2 file may crash the application or potentially run attacker-controlled code when opened. Business risk depends on whether this legacy viewer is installed and whether users receive untrusted JB2/JBIG2 files.
Executive priority
Prioritize as legacy endpoint exposure cleanup, not a confirmed emergency. Escalate if STDU Viewer 1.6.375 is deployed broadly or used to process externally supplied documents.
Technical view
The CVE description links the flaw to crafted .jb2 parsing and notes that data from the faulting address can control code flow at STDUJBIG2File+0x15e9. Public metadata does not provide CVSS, CWE, patch status, or detailed affected CPEs.
Likely exposure
Exposure is likely limited to endpoints running STDU Viewer 1.6.375 where users can open .jb2 files. The source bundle lists affected vendor/product as n/a, so confirmation requires endpoint software inventory rather than CPE matching alone.
Exploitation context
The sources describe arbitrary code execution or denial of service through a crafted file. They do not show CISA KEV listing, confirmed active exploitation, exploit maturity, or weaponized public use, so active exploitation should not be assumed.
Researcher notes
Evidence is sparse. The CVE record identifies the vulnerable version and crash control-flow symptom, but lacks CVSS, CWE, vendor advisory, patch details, and CPEs. Avoid broad product claims beyond STDU Viewer 1.6.375.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375.
- Check vendor guidance for a patched or supported replacement version.
- Restrict opening untrusted .jb2 or JBIG2 files.
- Remove the viewer where business use is not required.
- Use endpoint controls to limit risky file association handling.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 exists in endpoint inventory.
- Review file associations for .jb2 and JBIG2 content.
- Check whether users receive these files from external sources.
- Verify remediation against vendor guidance if available.
- Document exceptions for systems that must keep the viewer.
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-14295 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-14295CVE 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.