Security readout for executives and security teams
Plain-English summary
This issue affects STDU Viewer 1.6.375 when it processes a malicious JBIG2 .jb2 file. A user opening such a file could see the application crash, and the CVE text leaves open "possibly unspecified other impact." Sources do not provide severity scoring, patch status, or evidence of active exploitation.
Executive priority
Treat this as a targeted endpoint hygiene issue, not an emergency based on current evidence. Prioritize if STDU Viewer 1.6.375 is deployed broadly, used with untrusted documents, or present in high-risk user groups.
Technical view
CVE-2017-14310 is a file-parsing vulnerability in STDU Viewer 1.6.375. The reported failure is a read access violation in STDUJBIG2File around DllUnregisterServer+0x1869 when handling a crafted .jb2 file. Public data does not list a CWE, CVSS vector, root cause, fixed version, or reliable impact beyond denial of service and unspecified possible impact.
Likely exposure
Exposure is most likely on endpoints where STDU Viewer 1.6.375 is installed and users can open externally supplied .jb2 files. Server-side exposure is not indicated by the provided sources.
Exploitation context
The sources describe a crafted-file trigger, which normally requires user interaction or a workflow that automatically opens .jb2 files. The CVE is not listed as KEV in the supplied bundle, and no cited source here confirms active exploitation.
Researcher notes
Evidence is sparse. The public CVE record names STDU Viewer 1.6.375, a crafted .jb2 file, denial of service, and a read access violation location. It does not establish exploit maturity, affected version range, fixed build, CWE, or whether memory corruption has security impact beyond crash behavior.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375 installations.
- Restrict opening untrusted .jb2 files in STDU Viewer.
- Check vendor or maintainer guidance for updates or replacement recommendations.
- Use endpoint controls to quarantine unexpected JBIG2 attachments or downloads.
- Remove STDU Viewer where there is no business need.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 is present in software inventory.
- Review file association settings for .jb2 and related JBIG2 files.
- Search email and download controls for unexpected .jb2 delivery attempts.
- Check endpoint crash telemetry for STDU Viewer failures involving JBIG2 files.
- Verify any remediation against vendor-published guidance, if 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-14310 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-14310CVE 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.