CVE-2017-10749
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 execute arbitrary code or cause a denial of service via a crafted .rle file, related to a "User Mode Write AV near NULL starting at wow64!Wow64NotifyDebugger+0x000000000000001d."
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 in its RLE (Run-Length Encoding) image file parser. A specially crafted .RLE file triggers a write access violation near a null pointer address (wow64!Wow64NotifyDebugger), which can be leveraged for arbitrary code execution or causes a denial of service condition.
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 is installedCheck for XnView installation directory (commonly C:\Program Files\XnView or C:\Program Files (x86)\XnView) or search for xnview.exe using file explorer or Get-ChildItem -Recurse in PowerShellAffected if XnView Classic executable is found on the system
-
Confirm installed version is 2.40Right-click xnview.exe, select Properties, go to Details tab, and check File Version. Alternatively, run xnview.exe and check Help > About, or use PowerShell: (Get-Item 'C:\Program Files\XnView\xnview.exe').VersionInfo.FileVersionAffected if File version shows exactly 2.40
-
Identify if RLE file support is presentCheck if RLE decoder module exists in the XnView installation folder (look for files related to RLE or check Help > Formats > List to see supported formats)Affected if RLE format is listed as supported or RLE-related files exist in the XnView program directory
-
Determine if RLE files are processedSearch the system for .RLE files using PowerShell: Get-ChildItem -Path $env:USERPROFILE -Recurse -Filter *.rle -ErrorAction SilentlyContinue. Also check recent file history or downloads foldersAffected if RLE image files exist on the system and could be opened with XnView
A user is affected if XnView Classic version 2.40 is installed AND the RLE image format parser is available and could be used to open .RLE files.
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 dataAvoid opening untrusted or unexpected .RLE files in XnView Classic. Evaluate migrating to a patched version of XnView or an alternative image viewer that receives regular security updates.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10749 — 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-10749 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