CVE-2018-11705
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 · uneditedFastStone Image Viewer 6.2 has a User Mode Write AV at 0x00578cc4, triggered when the user opens a malformed JPEG file that is mishandled by FSViewer.exe. Attackers could exploit this issue for DoS (Access Violation) or possibly unspecified other impact.
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 confidenceFastStone Image Viewer 6.2 contains a memory corruption vulnerability during JPEG file parsing. When processing a malformed JPEG file, the application triggers a User Mode Write Access Violation at a specific memory address (0x00578cc4), indicating an out-of-bounds write due to insufficient bounds checking on image data structures during 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= 6.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 FastStone Image Viewer installationCheck if FastStone Image Viewer is installed by looking for FSViewer.exe in common installation directories such as C:\Program Files\FastStone Image Viewer\ or C:\Program Files (x86)\FastStone Image Viewer\Affected if The application is present on the system
-
Identify the installed versionRight-click on FSViewer.exe, select Properties, then navigate to the Details tab to view the File Version, or run the application and check Help > About FastStone Image ViewerAffected if The version is exactly 6.2 (build 1 or any subversion)
-
Determine JPEG file handling usageSearch for .jpg or .jpeg files on the system, or check recent file access history in the application if available, to confirm the user works with JPEG imagesAffected if The user opens, views, or processes JPEG files using FastStone Image Viewer
-
Verify JPEG parsing functionality is accessibleAttempt to open any JPEG file with FastStone Image Viewer to confirm the JPEG parsing code path is reachable and in active useAffected if The user can successfully load and view JPEG images through the application
A user is affected if FastStone Image Viewer version 6.2 is installed and they open or process JPEG files with the application, as the vulnerability is triggered during JPEG parsing.
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 malformed JPEG files with FastStone Image Viewer. Check vendor for available patches and consider upgrading to the latest version, or use an alternative image viewer if no patch is available.
- Consultation2.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11705 — 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-2018-11705 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