dbcve.org
XnviewApplication

CVE-2017-14272

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 execute arbitrary code or cause a denial of service via a crafted .jb2 file, related to a "User Mode Write AV starting at jbig2dec+0x000000000000595d."

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 confidence

XnView Classic 2.40 contains a memory corruption vulnerability in its JBIG2 decoder (jbig2dec) when processing crafted .jb2 files. Attackers can trigger a user-mode write access violation, leading to arbitrary code execution or denial of service. The vulnerability stems from insufficient bounds checking during JBIG2 image decoding.

MitigationDeploy updated XnView version with patched jbig2dec library, or implement application whitelisting to block untrusted .jb2 files and restrict XnView execution to trusted sources.

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. Locate XnView installation
    Search for XnView executable (xnview.exe) on the system - typically found in Program Files or Program Files (x86) directories
    Affected if XnView is installed and the executable exists
  2. Retrieve installed version number
    Right-click xnview.exe, select Properties, then view the Details tab to find the File Version, or run 'xnview.exe /?' or check Add/Remove Programs
    Affected if Version is exactly 2.40
  3. Verify JBIG2 decoder component exists
    Check for jbig2dec library or JBIG2-related DLL files in the XnView installation directory (such as jbig2dec.dll or similar)
    Affected if JBIG2 decoder component is present in the XnView installation folder
  4. Check .jb2 file association
    Attempt to open a .jb2 file with XnView or check file type associations in XnView settings to confirm JBIG2 image format support is enabled
    Affected if XnView is configured to process or open .jb2 files

If XnView version 2.40 is installed with the JBIG2 decoder component present and .jb2 file handling is enabled, the environment is affected by CVE-2017-14272.

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

Deploy updated XnView version with patched jbig2dec library, or implement application whitelisting to block untrusted .jb2 files and restrict XnView execution to trusted sources.

Fix this in Xnview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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