LiveActive security incident?Get immediate response
CVE Record

CVE-2017-14298: STDU Viewer 1.6.375 allows attackers to execute arbitrary code or cause a denial of service via a crafted ....

STDU Viewer 1.6.375 allows attackers to execute arbitrary code or cause a denial of service via a crafted .jb2 file, related to "Data from Faulting Address controls subsequent Write Address starting at STDUJBIG2File!DllGetClassObject+0x00000000000038e8."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a memory corruption issue in STDU Viewer 1.6.375 when handling crafted .jb2 files. A successful attack could run code on a user workstation or crash the viewer. The supplied sources do not provide CVSS scoring, confirmed active exploitation, or vendor fix details.

Executive priority

Treat this as a targeted endpoint exposure issue, not an enterprise-wide emergency based on the supplied evidence. Prioritize inventory and removal or containment where STDU Viewer 1.6.375 is present, especially in environments that handle external documents.

Technical view

The CVE text ties the issue to STDUJBIG2File processing, where data from a faulting address can influence a later write address. That indicates unsafe memory handling during JBIG2 file parsing. Impact is listed as arbitrary code execution or denial of service via a crafted .jb2 file.

Likely exposure

Exposure is most likely on endpoints with STDU Viewer 1.6.375 installed and used to open .jb2/JBIG2 files, especially files received from email, web downloads, or external parties. The source bundle does not provide CPEs or broader affected version data.

Exploitation context

The provided CVE data does not show CISA KEV listing or cited evidence of active exploitation. It does indicate a file-parsing attack path involving a crafted .jb2 file, so risk depends on whether users can open untrusted JBIG2 content with STDU Viewer.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE, patch reference, or active exploitation source is included. The useful technical clue is attacker influence over a subsequent write address in STDUJBIG2File, consistent with memory corruption during crafted JBIG2 parsing.

Mitigation direction

  • Identify endpoints running STDU Viewer 1.6.375.
  • Check vendor or maintainer guidance for fixed versions or retirement advice.
  • Remove the viewer where there is no business need.
  • Restrict opening untrusted .jb2 files on managed endpoints.
  • Review file associations for JBIG2 content.

Validation and detection

  • Confirm installed STDU Viewer versions through software inventory.
  • Check whether .jb2 files open by default in STDU Viewer.
  • Review email and endpoint telemetry for recent .jb2 file handling.
  • Document whether any business workflow requires JBIG2 viewing.
  • Verify compensating controls without opening suspicious samples.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2017-14298 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.