CVE-2017-14296
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 · uneditedSTDU 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+0x00000000000043e6."
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 confidenceSTDU Viewer 1.6.375 contains a memory corruption vulnerability in its JBIG2 image parser when processing crafted .jb2 files. The vulnerability stems from a write-what-where condition where data from a faulting address controls a subsequent write address, allowing attackers to achieve arbitrary code execution or cause a denial of service.
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= 1.6.375CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify STDU Viewer versionOpen STDU Viewer, then navigate to Help > About or check the program's file properties (right-click the executable > Properties > Details) to view the version numberAffected if Version is exactly 1.6.375
-
Locate STDU Viewer executableSearch for 'STDU Viewer.exe' or 'stdview.exe' in Program Files directories, or use 'where /r C:\ stdview.exe' in Command PromptAffected if The executable exists on the system, indicating STDU Viewer is installed
-
Verify JBIG2 file handling capabilityAttempt to open any .jb2 file with STDU Viewer, or check if .jb2 file extension is associated with STDU Viewer in Windows default programs settingsAffected if STDU Viewer can open or is associated with .jb2 files, meaning the vulnerable JBIG2 parser can be triggered
-
Check for recently opened .jb2 filesReview Windows recent documents, browser downloads folder, or STDU Viewer's recent files list (if available) for .jb2 files from untrusted sourcesAffected if Any .jb2 files have been opened, especially from unknown or untrusted sources
A user is affected if STDU Viewer version 1.6.375 is installed and the JBIG2 parser can be invoked by opening a crafted .jb2 file, enabling arbitrary code execution or denial of service.
Generated from the published advisory. Verify against your own configuration.
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 dataAvoid opening untrusted .jb2 files in STDU Viewer. Check for vendor updates; if unavailable, consider using alternative image viewers or running STDU Viewer in an isolated sandbox environment to limit exposure.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14296 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-14296 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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