CVE-2017-14290
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 "Heap Corruption starting at wow64!Wow64NotifyDebugger+0x000000000000001d."
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 heap corruption vulnerability when parsing crafted JB2 image files. The heap corruption occurs in the Windows WOW64 layer (wow64!Wow64NotifyDebugger), indicating the vulnerability can be triggered on 64-bit Windows systems. Successful exploitation could allow arbitrary code execution or cause application 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.
-
Confirm STDU Viewer is installedCheck for STDU Viewer in installed programs via Control Panel > Programs and Features, or search for stdviewer.exe in common installation paths like C:\Program Files\STDU Viewer or C:\Program Files (x86)\STDU ViewerAffected if STDU Viewer version 1.6.375 is present on the system
-
Verify the exact version numberRight-click stdviewer.exe, select Properties, then go to the Details tab to view the File Version. Alternatively, run 'wmic product get name,version' or check the application's About/Help menuAffected if The version reported is exactly 1.6.375
-
Check for JB2 file associationsSearch for .jb2 file associations in Windows Explorer: look for .jb2 files on the system, or check HKEY_CLASSES_ROOT\.jb2 in the Windows Registry to see if STDU Viewer is registered as the handler for .jb2 filesAffected if STDU Viewer is registered as the default handler for .jb2 files and such files can be opened directly with the application
-
Confirm Windows system architectureOpen System Properties (win + pause) or run 'systeminfo' in Command Prompt. Look for OS Name and System Type indicating 64-bit Windows (x64-based PC)Affected if Running a 64-bit version of Windows, which enables the WOW64 layer where the heap corruption occurs
You are affected if STDU Viewer version 1.6.375 is installed on a 64-bit Windows system and the application can open .jb2 files, as the vulnerability triggers when parsing a crafted JB2 image file.
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 unknown JB2 files with STDU Viewer. Since STDU Viewer appears to be an older/legacy application with no indicated patch, consider using alternative image viewers or isolated VM environments for viewing JB2 files from untrusted sources.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14290 — 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-14290 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