CVE-2017-14547
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 .mobi file, related to a "Read Access Violation starting at STDUMOBIFile!DllUnregisterServer+0x000000000002efc0."
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 read access violation vulnerability in its Mobi file parser. When parsing a specially crafted .mobi file, the software attempts to read from an invalid memory address, triggering a crash (denial of service). The access violation occurs at a specific offset within the STDUMOBIFile DLL, indicating insufficient bounds checking during file parsing.
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 installation and versionCheck if STDU Viewer version 1.6.375 is installed by examining program files directories or using system inventory tools to list installed software and its versionAffected if STDU Viewer version 1.6.375 is installed on the system
-
Locate the STDUMOBIFile DLLSearch for STDUMOBIFile.dll in the STDU Viewer installation directory (typically under Program Files or Program Files (x86))Affected if STDUMOBIFile.dll exists in the STDU Viewer installation folder, confirming the vulnerable Mobi parsing component is present
-
Check if .mobi file handling is enabled or usedVerify that STDU Viewer has file association handlers registered for .mobi files, or check recent file access logs for .mobi file processingAffected if STDU Viewer is configured to handle .mobi files (file associations exist) or has recently opened .mobi files
-
Identify active processes or recent crash logsReview system event logs or application crash reports for access violations originating from STDU Viewer or STDUMOBIFile.dll when processing .mobi filesAffected if Crash logs or access violation events show STDUMOBIFile.dll as the faulting module while processing .mobi content
You are affected if STDU Viewer version 1.6.375 is installed with the STDUMOBIFile.dll component and the system processes or is configured to open .mobi files using this vulnerable software.
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 unsolicited .mobi files with STDU Viewer. Consider using alternative document viewers or implementing file validation before processing.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14547 — 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-14547 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