CVE-2017-14301
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!DllUnregisterServer+0x00000000000076d3."
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 · moderate confidenceSTDU Viewer 1.6.375 contains a memory corruption vulnerability when parsing JBIG2 (.jb2) image files. The vulnerability creates a write-what-where condition where data from a faulting address controls a subsequent write address, allowing arbitrary code execution or denial of service. The flaw resides in the JBIG2 parsing component.
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.
-
Locate STDU Viewer installationCheck common installation directories such as C:\Program Files\STDU Viewer or C:\Program Files (x86)\STDU Viewer, or search for 'STDU Viewer' in Add/Remove Programs (Windows) or the Applications folder (if applicable).Affected if STDU Viewer is found installed on the system.
-
Determine installed versionRight-click the STDU Viewer executable (typically named STDUViewer.exe), select Properties, and inspect the File Version or Product Version field in the Details tab. Alternatively, launch STDU Viewer and check Help > About for the version number.Affected if The version number matches exactly 1.6.375.
-
Verify JBIG2 file association or usageCheck if .jb2 files are associated with STDU Viewer by examining the file type associations in the application or Windows default programs settings. Also check if the JBIG2 decoding module is present in the installation directory.Affected if JBIG2 (.jb2) files are associated with STDU Viewer or the JBIG2 parsing component is present and accessible.
-
Confirm parsing capability is activeAttempt to open any .jb2 file with STDU Viewer or check recent file history within the application for .jb2 file usage.Affected if STDU Viewer can successfully load and display JBIG2 images, indicating the vulnerable parsing code path is present.
A system is affected only if STDU Viewer version 1.6.375 is installed AND the JBIG2 parsing functionality is present and capable of opening .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 dataAvoid opening untrusted or unexpected .jb2 files with STDU Viewer. Consider using alternative image viewing software with active security maintenance if handling untrusted JBIG2 content.
- Consultation4.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14301 — 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-14301 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