CVE-2017-10778
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 might allow attackers to cause a denial of service or possibly have unspecified other impact via a crafted .rle file, related to "Data from Faulting Address controls Branch Selection starting at xnview+0x0000000000233125."
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 confidenceXnView Classic 2.40 contains a memory corruption vulnerability when parsing specially crafted .rle image files. The vulnerability allows attacker-controlled data at a faulting address to influence branch selection, leading to denial of service or potential arbitrary 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.
-
Confirm XnView Classic installation and versionCheck for XnView Classic installation directory (typically C:\Program Files\XnView or C:\Program Files (x86)\XnView) and locate xnview.exe. Right-click the executable, select Properties, and check the File Version in the Details tab.Affected if The installed version is 2.40 exactly.
-
Verify RLE file handling capability existsSearch for RLE-related files in the XnView program directory, including plug-ins folder (usually <install_path>\Plugins\) for RLE format support modules.Affected if RLE parsing modules or plugins are present in the XnView installation.
-
Check for recently opened .rle filesReview Windows recent files or search the system for .rle image files using File Explorer search (type: .rle in search box). Check browser download folders and mail attachments for .rle files.Affected if Any .rle files exist on the system that could be opened by XnView.
-
Determine if XnView is set as default handler for RLERight-click any .rle file in Windows Explorer, select Properties, then open With to see if XnView Classic is listed as an available or default program for .rle files.Affected if XnView Classic is associated as an opener for .rle file extensions.
-
Check for untrusted or downloaded RLE contentExamine folders where untrusted files are commonly received: browser download directories, email attachment folders, and network shares from untrusted sources.Affected if Users have access to or commonly process .rle files from untrusted or external sources using XnView.
A user is affected if XnView Classic version 2.40 is installed AND the RLE file format handler is present AND the user opens or could open specially crafted .rle files with this application.
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 dataDo not open untrusted .rle files in XnView Classic. Apply vendor patches when available or consider using an alternative image viewer with active security support.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10778 — 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-10778 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