CVE-2017-14553
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 .djvu file, related to a "User Mode Write AV starting at STDUDjVuFile!DllUnregisterServer+0x00000000000085f5."
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 specially crafted .djvu files. The flaw triggers a User Mode Write Access Violation at a specific memory offset, which can be leveraged for 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.
-
Verify STDU Viewer is installedCheck for STDU Viewer executable (stdviewer.exe) in common installation directories such as C:\Program Files\STDU Viewer or C:\Program Files (x86)\STDU Viewer, or search for it using Get-ChildItem -Recurse -Filter stdviewer.exe on systems drives.Affected if STDU Viewer executable is found on the system
-
Confirm installed version numberRight-click stdviewer.exe, select Properties, then navigate to the Details tab to read the File Version field. Alternatively, run (Get-Item 'C:\Program Files\STDU Viewer\stdviewer.exe').VersionInfo or use PowerShell's Get-FileMetaDataReturnObject to retrieve version details.Affected if The version listed is exactly 1.6.375
-
Verify .djvu file association or usageCheck if STDU Viewer is set as the default handler for .djvu files by reviewing registry keys under HKCR\.djvu\OpenWithProgids or HKCR\Applications\stdviewer.exe, or by asking users if they open .djvu files with STDU Viewer.Affected if STDU Viewer is configured as the default .djvu file handler or users commonly open .djvu files using this application
-
Review recent .djvu file openingsInspect browser download history, email attachments, or file system access logs (such as Windows Event Log Security/Process Tracking if enabled) for evidence of recent .djvu file access via STDU Viewer.Affected if Users have opened .djvu files in STDU Viewer recently and the source of those files is untrusted or unknown
The system is affected only if STDU Viewer version 1.6.375 is installed AND users open untrusted .djvu files with this application.
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 .djvu files in STDU Viewer until an official vendor patch is available. Consider using alternative .djvu viewers or implement application whitelisting to restrict execution.
- 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-14553 — 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-14553 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