Security readout for executives and security teams
Plain-English summary
This CVE describes a flaw in STDU Viewer 1.6.375 where a malicious .jb2 file could crash the application or potentially run attacker-controlled code. The practical risk is highest where users still open untrusted JBIG2 documents with this older viewer.
Executive priority
Treat this as a targeted endpoint hygiene issue, not a confirmed internet-wide emergency. Prioritize removal or replacement if STDU Viewer 1.6.375 exists in environments that process external documents.
Technical view
The record links the issue to crafted .jb2 parsing in STDUJBIG2File, where data from a faulting address can control code flow near DllGetClassObject. The published description states possible arbitrary code execution or denial of service, but provides no CVSS, CWE, patch, or detailed vendor remediation.
Likely exposure
Likely limited to endpoints with STDU Viewer 1.6.375 installed, especially users who receive or open .jb2 files from email, downloads, or archives. The source bundle does not identify broader affected versions or CPEs.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The reported attack requires a crafted .jb2 file and user or workflow interaction with STDU Viewer.
Researcher notes
Evidence is sparse: the CVE description names STDU Viewer 1.6.375 and a crafted .jb2 trigger, but the affected metadata is empty and no official fix is provided in the bundle. Avoid expanding scope beyond the named version without separate confirmation.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375.
- Check vendor or trusted advisory sources for fixed versions or retirement guidance.
- Avoid opening untrusted .jb2 files in STDU Viewer.
- Use email and web controls to flag unexpected .jb2 attachments.
- Prefer supported document viewers for JBIG2 content.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 is installed on managed endpoints.
- Review file association settings for .jb2 files.
- Search email and endpoint telemetry for unexpected .jb2 files.
- Check vulnerability scanner results for this CVE or STDU Viewer evidence.
- Verify any vendor guidance before marking the issue remediated.
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-14297 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-14297CVE 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.