Security readout for executives and security teams
Plain-English summary
Opening a malicious .jb2 document in STDU Viewer 1.6.375 could crash the application or potentially run attacker-controlled code. Business urgency depends on whether this legacy viewer is still installed and whether users may open untrusted JB2 files.
Executive priority
Treat this as a targeted legacy-software risk. Prioritize discovery and removal or upgrade if the viewer is present, especially on systems exposed to email attachments, downloads, or document intake workflows.
Technical view
The CVE describes memory corruption in STDUJBIG2File handling .jb2 input, where data from a faulting address controls a later write address near DllGetClassObject+0x384b. The stated impacts are arbitrary code execution or denial of service. The record lacks CVSS, CWE, CPE, patch, and vendor remediation metadata.
Likely exposure
Exposure is likely limited to endpoints with STDU Viewer 1.6.375 installed, especially systems handling untrusted or externally supplied .jb2 files. The source bundle does not identify broader affected versions or products.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. Public details indicate a crafted-file attack surface, but available evidence is incomplete and should not be treated as proof of exploitation in the wild.
Researcher notes
The advisory data is sparse: no CVSS, CWE, CPE, affected-version range, or named fix is provided. Analysis should remain limited to STDU Viewer 1.6.375 and crafted .jb2 handling unless additional vendor or primary-source evidence is found.
Mitigation direction
- Inventory endpoints for STDU Viewer 1.6.375 installations.
- Check vendor or trusted software-maintenance guidance for fixed versions or retirement advice.
- Remove the viewer where it is not business-required.
- Restrict opening of untrusted .jb2 files on managed endpoints.
- Use endpoint controls to limit execution from document-handling workflows.
Validation and detection
- Confirm whether STDU Viewer 1.6.375 exists in software inventory.
- Identify users or systems that handle JB2 files from external sources.
- Review EDR, email, and web logs for suspicious JB2 file delivery.
- Verify any vendor-recommended update, removal, or compensating control is applied.
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-14299 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-14299CVE 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.