dbcve.org
XnviewApplication

CVE-2017-14283

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

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
XnView Classic for Windows Version 2.40 allows attackers to cause a denial of service or possibly have unspecified other impact via a crafted .jb2 file, related to a "Read Access Violation starting at jbig2dec+0x0000000000008fe4."

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

XnView Classic v2.40 contains a memory corruption vulnerability in its JBIG2 image decoder (jbig2dec) when parsing specially crafted .jb2 files, causing a read access violation that can lead to denial of service or potentially arbitrary code execution.

MitigationUpdate XnView Classic to a version that patches this vulnerability; avoid opening untrusted .jb2 files from unknown sources until the patch is applied.

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
XnviewApplication
Affected:= 2.40

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

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

  1. Confirm XnView Classic is installed
    Look for XnView Classic in the installed programs list (Windows: Control Panel > Programs and Features, or check the installation directory typically at C:\Program Files\XnView or C:\Program Files (x86)\XnView)
    Affected if XnView Classic v2.40 is installed on the system
  2. Identify the exact XnView version
    Right-click on the XnView executable (xnview.exe), select Properties, and check the File Version tab, or launch XnView and go to Help > About to view the version number
    Affected if The installed version is exactly 2.40
  3. Check for JBIG2 (.jb2) file support
    In XnView, go to Options > Settings > General and look for JBIG2 decoder settings, or attempt to open a .jb2 file to see if XnView attempts to process it
    Affected if The JBIG2 decoder is present and XnView can open .jb2 files
  4. Inspect recently opened .jb2 files
    Check the XnView history or recent files list (View > Browser > History) for any .jb2 files that may have been opened
    Affected if Any .jb2 files have been opened with XnView Classic v2.40

If XnView Classic version 2.40 is installed and can process JBIG2 (.jb2) files, the environment is affected by this vulnerability.

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

Update XnView Classic to a version that patches this vulnerability; avoid opening untrusted .jb2 files from unknown sources until the patch is applied.

Fix this in Xnview Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-14283 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