CVE-2017-14549
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 "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 · high confidenceSTDU Viewer 1.6.375 contains a heap corruption vulnerability when parsing specially crafted .djvu files. The corruption occurs in the wow64 layer (32-bit application on 64-bit Windows), specifically at the Wow64NotifyDebugger function offset, allowing attackers to achieve arbitrary code execution or cause denial of service via a malformed file.
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 installationSearch for the STDU Viewer executable (stduviewer.exe) in common installation directories such as C:\Program Files\STDU Viewer or C:\Program Files (x86)\STDU Viewer, or use the Windows Programs and Features control panel to list installed software.Affected if STDU Viewer is present on the system
-
Confirm installed versionRight-click on stduviewer.exe, select Properties, then navigate to the Details tab to view the File Version. Alternatively, right-click the software entry in Programs and Features and select Properties to view the version.Affected if The version is exactly 1.6.375
-
Verify Windows architectureOpen System Information (msinfo32.exe) and check the System Type field. The vulnerability exists in the Wow64 layer which only applies when a 32-bit application runs on a 64-bit Windows system.Affected if Running 64-bit Windows with a 32-bit version of STDU Viewer
-
Check .djvu file handlingRight-click any .djvu file, select Open with > Choose another app, or inspect file associations in the Windows Registry under HKEY_CLASSES_ROOT\.djvu to confirm STDU Viewer is associated with .djvu files.Affected if STDU Viewer is set as the default or alternate handler for .djvu files
You are affected if STDU Viewer version 1.6.375 is installed on a 64-bit Windows system and configured to open .djvu 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 dataUntil an official vendor patch is released (unlikely for this discontinued software), users should migrate to an alternative .djvu viewer and implement file-type restrictions to prevent untrusted .djvu files from opening in STDU Viewer, or uninstall the vulnerable software entirely.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14549 — 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-14549 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