Security readout for executives and security teams
Plain-English summary
This CVE describes a crash risk in XnView Classic for Windows 2.40 when handling a specially crafted .rle image file. The public record mainly supports denial of service. It also mentions possible unspecified impact, but does not define what that means.
Executive priority
Treat this as a targeted hygiene issue unless XnView Classic 2.40 is widely deployed or used with external image files. Prioritize inventory and vendor-version review before urgent response actions.
Technical view
The issue is tied to crafted .rle parsing in XnView Classic 2.40, with faulting-address data influencing branch selection around IMM32!ImmLockImeDpi. Public metadata provides no CVSS, CWE, confirmed code execution, patch version, or detailed affected-product CPEs.
Likely exposure
Exposure is most likely on Windows endpoints where XnView Classic 2.40 is installed and users can open untrusted .rle files. The source bundle does not identify server-side exposure or broader affected versions.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. Available evidence indicates a crafted-file attack scenario requiring the vulnerable application to process a malicious .rle file.
Researcher notes
Evidence is sparse. The CVE names XnView Classic 2.40 and a crafted .rle trigger, but affected metadata is n/a and no official fix, CVSS, CWE, or exploit status is included in the bundle.
Mitigation direction
- Inventory endpoints for XnView Classic for Windows 2.40.
- Check XnView vendor guidance for fixed versions or replacement recommendations.
- Restrict opening untrusted .rle files in XnView Classic.
- Route externally supplied image files through controlled analysis workflows.
- Remove the vulnerable application where it is not business-required.
Validation and detection
- Review software inventory for XnView Classic 2.40 on Windows endpoints.
- Check file associations for .rle files handled by XnView Classic.
- Confirm whether users receive or process untrusted .rle files.
- Document that public sources lack CVSS, CWE, and patch details.
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.
CVE-2017-10765 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-10765CVE 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.