dbcve.org
Stdu ViewerApplication · Stdutility

CVE-2017-14299

HIGH · 7.8 CVSS v3.0 Published 2017-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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+0x000000000000384b."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

STDU Viewer 1.6.375 contains a memory corruption vulnerability in its JBIG2 image file (.jb2) parsing component (STDUJBIG2File!DllGetClassObject). The vulnerability allows a crafted .jb2 file to trigger a write-what-where condition where data from a faulting address controls a subsequent write address, leading to arbitrary code execution or denial of service.

MitigationApply vendor patch or update STDU Viewer to the latest version. If no update is available, restrict handling of .jb2 files to trusted sources or consider using an alternative viewer without JBIG2 support.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Stdu ViewerApplication
Affected:= 1.6.375

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if STDU Viewer is installed
    Look for STDU Viewer in the list of installed programs (Windows: Control Panel > Programs and Features, or check Program Files directory for STDU Viewer folder)
    Affected if STDU Viewer is present on the system
  2. Identify the installed version
    Right-click the STDU Viewer executable, select Properties, and check the File Version under the Details tab. Alternatively, open STDU Viewer and look in Help > About
    Affected if The version listed is exactly 1.6.375
  3. Check for .jb2 file association or recent .jb2 file handling
    Search for .jb2 files on the system (use file search for *.jb2) and verify if STDU Viewer is associated to open them, or check recent file history in the application
    Affected if STDU Viewer 1.6.375 is configured to handle or has recently opened .jb2 files

A system is affected if STDU Viewer version 1.6.375 is installed and can be used to open or process .jb2 image files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch or update STDU Viewer to the latest version. If no update is available, restrict handling of .jb2 files to trusted sources or consider using an alternative viewer without JBIG2 support.

Fix this in Stdu Viewer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14299 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-14299 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data