CVE-2017-14692
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 "User Mode Write AV starting at STDUJBIG2File!DllGetClassObject+0x000000000000653b."
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 confidenceA memory corruption vulnerability in STDU Viewer 1.6.375 allows arbitrary code execution or denial of service via a crafted JB2 image file. The vulnerability manifests as a user mode write access violation in the JBIG2 file parsing component (STDUJBIG2File.dll), indicating a buffer overflow or out-of-bounds write condition that can be triggered when parsing malicious JB2 files.
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 installationCheck if STDU Viewer is installed on the system by looking for the application in Program Files (typically C:\Program Files\STDU Viewer or C:\Program Files (x86)\STDU Viewer), or by searching for STDU Viewer in the Start Menu or installed programs list.Affected if STDU Viewer is installed on the system
-
Identify installed STDU Viewer versionRight-click on the STDU Viewer executable (typically STDUViewerApp.exe) in the installation directory, select Properties, and check the File Version in the Details tab. Alternatively, open STDU Viewer and go to Help > About to view the version number.Affected if The installed version is exactly 1.6.375
-
Locate the vulnerable JBIG2 componentNavigate to the STDU Viewer installation directory and search for the file STDUJBIG2File.dll. This DLL handles JB2/JBIG2 image parsing and contains the vulnerable code.Affected if STDUJBIG2File.dll exists in the STDU Viewer installation directory (indicating JB2/JBIG2 support is present)
-
Confirm JB2 file association or usageCheck if STDU Viewer has registered handlers for .jb2 or .jbig2 file extensions, or if the application has been used to open JB2 files. This can be verified by examining file associations in Windows or by checking recent files within the application.Affected if JB2 file handling is enabled or has been used with STDU Viewer
A user is affected if STDU Viewer version 1.6.375 is installed with the STDUJBIG2File.dll component present and JB2 file handling is available, enabling the buffer overflow vulnerability when parsing malicious 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 dataApply vendor patches when available; until then, avoid opening untrusted JB2 files with STDU Viewer. Consider using application whiteliting or sandboxing to limit exposure to this file parsing vulnerability.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14692 — 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-14692 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