CVE-2017-14579
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 a "Read Access Violation on Control Flow starting at STDUJBIG2File!DllGetClassObject+0x0000000000005b70."
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 parsing component (STDUJBIG2File.dll). When processing a specially crafted .jb2 file, the parser triggers a read access violation on the control flow, which can be exploited for arbitrary code execution or cause a denial of service condition.
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.
-
Verify STDU Viewer versionCheck the installed version of STDU Viewer through the program's About dialog, installer records, or uninstall entry in the system Control PanelAffected if The installed version is exactly 1.6.375 (other versions are not affected by this specific CVE)
-
Locate the JBIG2 parsing componentSearch for STDUJBIG2File.dll in the STDU Viewer installation directory (commonly C:\Program Files\STDU Viewer or similar)Affected if The file STDUJBIG2File.dll exists in the STDU Viewer directory, confirming the vulnerable component is present
-
Confirm JBIG2 file handling is enabledCheck if JBIG2 file associations are active in the system - look for .jb2 file type registration in Windows registry under HKCR\.jb2 or check if STDU Viewer is set as the default handler for JBIG2 filesAffected if STDU Viewer is associated with or configured to open .jb2 files, enabling the attack surface
-
Detect recent JBIG2 file activityReview Windows Event Viewer, recent documents list, or file history for any .jb2 files opened with STDU ViewerAffected if Any .jb2 files have been opened with STDU Viewer, indicating potential exploitation opportunity
You are affected if STDU Viewer version 1.6.375 is installed and JBIG2 file support is enabled or has been used to open .jb2 files
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 dataUsers should avoid opening untrusted .jb2 files in STDU Viewer until a patched version is released. Consider disabling file association handling for JBIG2 files or using an alternative viewer that has regular security updates.
- Consultation2.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14579 — 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-14579 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