CVE-2017-14544
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 .epub file, related to "Data from Faulting Address is used as one or more arguments in a subsequent Function Call starting at STDUEPubFile!DllUnregisterServer+0x000000000003fff1."
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 crafted .epub files. Data from a faulting address (likely beyond buffer bounds) is used as arguments in a subsequent function call, leading to denial of service or potentially arbitrary code execution.
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.
-
Check if STDU Viewer is installedSearch for STDU Viewer executable in common installation paths: C:\Program Files\STDU Viewer\, C:\Program Files (x86)\STDU Viewer\, or check Start Menu for STDU Viewer entry. Also check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for STDU Viewer entry.Affected if STDU Viewer is found on the system
-
Determine installed STDU Viewer versionRight-click on the STDU Viewer executable (typically StdUView.exe), select Properties, then view the Details tab to see the File Version. Alternatively, check the Uninstall entry in Windows Registry for the DisplayVersion value.Affected if Version is exactly 1.6.375
-
Verify .epub file association existsCheck if .epub files are associated with STDU Viewer by right-clicking any .epub file in Windows Explorer, selecting Properties, and looking at 'Opens with' or by checking HKEY_CLASSES_ROOT\.epub in Windows Registry for the default handler.Affected if .epub files are configured to open with STDU Viewer
-
Identify recently opened .epub filesCheck the application's recent files list, typically found in File > Open Recent within STDU Viewer, or examine Windows Jump Lists and recent documents in the user's AppData folder for .epub file paths.Affected if Any .epub files have been opened with STDU Viewer
User is affected if STDU Viewer version 1.6.375 is installed AND .epub file handling is enabled, meaning the memory corruption vulnerability can be triggered by opening a crafted .epub 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 .epub files with STDU Viewer until an official patch is available; consider using alternative document viewers with updated security features for handling untrusted files.
- 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-14544 — 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-14544 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