Security readout for executives and security teams
Plain-English summary
CVE-2017-10746 is a flaw in XnView Classic for Windows 2.40. A malicious RLE image file could crash the application or potentially run code on a user’s Windows system if opened.
Executive priority
Treat this as a targeted legacy-software risk. It is not listed in KEV, but arbitrary code execution from a file-open workflow warrants inventory and removal or upgrade decisions.
Technical view
The CVE describes arbitrary code execution or denial of service via a crafted .rle file, tied to a user-mode write access violation in ntdll RtlEnterCriticalSection during handling by XnView Classic 2.40.
Likely exposure
Exposure is most likely where Windows endpoints still run XnView Classic 2.40 and users can open RLE files from email, web downloads, shared drives, or external media.
Exploitation context
The source bundle includes a public GitHub advisory reference but no KEV listing and no cited evidence of active exploitation. User interaction appears required because the trigger is opening a crafted .rle file.
Researcher notes
The provided data lacks CVSS, CWE, patch, and exploit-in-the-wild details. Analysis should stay anchored to XnView Classic for Windows 2.40 and crafted .rle parsing unless additional vendor or advisory evidence is obtained.
Mitigation direction
- Inventory Windows endpoints for XnView Classic 2.40.
- Check XnView vendor guidance for fixed versions or removal recommendations.
- Restrict opening untrusted .rle files on managed endpoints.
- Prefer supported image viewers for workflows handling external files.
- Apply endpoint controls to quarantine suspicious image attachments.
Validation and detection
- Confirm whether XnView Classic 2.40 is installed on managed Windows systems.
- Review file associations for .rle files on affected endpoints.
- Check email and web controls for RLE attachment handling.
- Verify remediation against vendor guidance when available.
- Document any business workflows that still require RLE files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-10746 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wlinzi/security_advisories/tree/master/CVE-2017-10746CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.