CVE-2017-14309
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 cause a denial of service or possibly have unspecified other impact via a crafted .jb2 file, related to a "Read Access Violation starting at STDUJBIG2File!DllUnregisterServer+0x0000000000006ec8."
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 in its JBIG2 image parsing component (STDUJBIG2File.dll). Attackers can trigger a Read Access Violation by supplying a specially crafted .jb2 file, causing denial of service or potentially achieving arbitrary code execution. The vulnerability occurs during image processing when the application attempts to read from an invalid memory address.
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 installationOpen Windows Programs and Features (appwiz.cpl) or check Program Files folder for STDU Viewer installation directory. Look for Stdutility or STDU Viewer folder.Affected if STDU Viewer version 1.6.375 is installed
-
Check executable versionRight-click the STDU Viewer executable (typically STDUViewer.exe in the installation folder, commonly in C:\Program Files\STDU Viewer or C:\Program Files (x86)\STDU Viewer), select Properties, and review the File Version field on the Details tab.Affected if File version shows exactly 1.6.375
-
Confirm vulnerable DLL presenceNavigate to the STDU Viewer installation directory and verify that STDUJBIG2File.dll exists in the same folder as the main executable.Affected if STDUJBIG2File.dll is present in the installation folder
-
Check for .jb2 file associationOpen Default Programs in Windows Control Panel, or right-click any .jb2 file in File Explorer and select Properties to see which application is associated with .jb2 files.Affected if STDU Viewer is associated as the default handler for .jb2 files
-
Inspect DLL file versionRight-click STDUJBIG2File.dll in the installation folder, select Properties, and check the File Version on the Details tab.Affected if DLL version matches 1.6.375 or cannot be determined (older unpatched build)
A user is affected if STDU Viewer version 1.6.375 is installed and the STDUJBIG2File.dll component exists, particularly if the application handles or is associated with .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 dataUpdate to a patched version of STDU Viewer if available; otherwise, implement file type restrictions to block untrusted .jb2 files or migrate to an alternative image viewer with active security support.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14309 — 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-14309 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