CVE-2017-14277
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 · uneditedXnView 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+0x0000000000005956."
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 confidenceXnView Classic for Windows Version 2.40 contains a memory corruption vulnerability in its jbig2dec library component when parsing crafted .jb2 (JBIG2) image files. The vulnerability manifests as a read access violation at jbig2dec+0x5956, indicating an out-of-bounds memory read during JBIG2 decoding, which can be triggered by a maliciously crafted file leading to denial of service or potential code execution.
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= 2.40CVSS 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 XnView Classic versionOpen XnView Classic, go to Help > About, or right-click the executable and check Properties > Details to confirm the version is 2.40Affected if The installed version is exactly 2.40 (other versions are not affected by this specific CVE)
-
Confirm jbig2dec library presenceSearch for jbig2dec.dll or jbig2_dec.dll in the XnView installation directory (typically C:\Program Files\XnView or C:\Program Files (x86)\XnView)Affected if The jbig2dec library file exists in the XnView directory, indicating JBIG2 decoding support is present
-
Check if JBIG2 file handling is enabledIn XnView, go to Options > General or File Associations and verify if .jb2 / JBIG2 image support is enabledAffected if JBIG2 support is enabled or .jb2 files are associated with XnView for opening
-
Test .jb2 file association behaviorRight-click any .jb2 file in Windows Explorer, select Open with > XnView Classic to see if XnView attempts to open itAffected if XnView attempts to open or preview .jb2 files, confirming the vulnerable parsing path could be triggered
You are affected if XnView Classic version 2.40 is installed with jbig2dec library present and JBIG2/.jb2 file support is enabled, allowing malicious .jb2 files to trigger the out-of-bounds read.
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 dataUsers should avoid opening untrusted .jb2 files in XnView Classic. The vendor should update the bundled jbig2dec library to a patched version that properly validates JBIG2 stream data before processing to prevent out-of-bounds memory access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14277 — 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-14277 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