Security readout for executives and security teams
Plain-English summary
CVE-2017-14303 affects STDU Viewer 1.6.375 when handling a crafted .jb2 file. The documented outcome is a crash or denial of service, with the CVE noting possible unspecified additional impact. Evidence is sparse, so treat this as a legacy document-viewer exposure rather than a confirmed enterprise-wide critical issue.
Executive priority
Handle as targeted hygiene for legacy desktop software. Prioritize remediation where external document handling is common, but do not treat it as actively exploited based on the provided evidence.
Technical view
The record describes a read access violation in STDUJBIG2File, reached through crafted JBIG2 .jb2 input in STDU Viewer 1.6.375. No CVSS, CWE, CPE, patch, or confirmed code execution details are provided in the source bundle.
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 provide CPE data or broader affected-version ranges.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The available description only supports crafted-file denial of service and possible unspecified impact.
Researcher notes
Public evidence is limited to the CVE description and referenced advisory. The impact language includes denial of service and possible unspecified other impact, but the bundle does not substantiate exploitability beyond the crash condition.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375 installations.
- Check vendor or project guidance for updates or replacement options.
- Avoid opening untrusted .jb2 files in STDU Viewer.
- Remove or replace STDU Viewer where business use is not required.
- Block or quarantine unexpected .jb2 attachments where feasible.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 exists in software inventory.
- Identify users or workflows that receive external .jb2 files.
- Review file associations for .jb2 on managed endpoints.
- Verify mail and web controls handle unexpected .jb2 files.
- Document compensating controls if no vendor fix is 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-14303 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-14303CVE 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.