Image ViewerApplication · Faststone

CVE-2017-8826

HIGH · 7.8 CVSS v3.0 Published 2017-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
FastStone Image Viewer 6.2 has a "User Mode Write AV" issue, possibly related to the jpeg_mem_term function in jmemnobs.c in libjpeg. This issue can be triggered by 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 · moderate confidence

FastStone Image Viewer 6.2 contains a memory corruption vulnerability in its bundled libjpeg library. When parsing a specially crafted malformed JPEG file, the jpeg_mem_term function in jmemnobs.c triggers a User Mode Write Access Violation, causing the application to crash or potentially allow unspecified further exploitation.

MitigationUsers should refrain from opening untrusted or unknown JPEG files with FastStone Image Viewer 6.2. Upgrade to a newer version of FastStone Image Viewer if available, or use an alternative image viewer for untrusted content until a vendor patch is released.

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
Image ViewerApplication
Affected:= 6.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FastStone Image Viewer installation
    Check if FastStone Image Viewer is installed on the system by looking for the application in Program Files or Program Files (x86), or by checking for the executable (FSViewer.exe or similar) in typical installation directories.
    Affected if FastStone Image Viewer is installed and the application can be located on the system.
  2. Identify installed version
    Right-click the FastStone Image Viewer executable, select Properties, and check the File Version in the Details tab. Alternatively, launch the application and look for the version number in the Help > About menu.
    Affected if The installed version is exactly 6.2 - this is the only affected version listed for this CVE.
  3. Locate bundled libjpeg library
    Search the FastStone Image Viewer installation directory for files with names containing 'jpeg' or 'libjpeg' (such as libjpeg.dll, jpeg.dll, or similar shared library files) that would indicate the presence of the bundled libjpeg library.
    Affected if A bundled libjpeg library file exists within the FastStone Image Viewer installation folder, confirming the vulnerable component is present.
  4. Verify the vulnerable jmemnobs.c component
    Inspect the bundled libjpeg library files for the presence of jmemnobs.c or compiled objects derived from it. This file contains the vulnerable jpeg_mem_term function mentioned in the CVE.
    Affected if Files related to jmemnobs.c or the jpeg_mem_term function are found in the bundled library, confirming the specific vulnerable code path exists.

A system is affected if FastStone Image Viewer version 6.2 is installed with its bundled libjpeg library present, making it vulnerable when parsing malformed JPEG files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should refrain from opening untrusted or unknown JPEG files with FastStone Image Viewer 6.2. Upgrade to a newer version of FastStone Image Viewer if available, or use an alternative image viewer for untrusted content until a vendor patch is released.

Fix this in Image Viewer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8826 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8826 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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