Security readout for executives and security teams
Plain-English summary
This CVE concerns XnView Classic for Windows 2.40 handling crafted RLE image files. A malicious .rle file may crash the application or cause unspecified additional impact. Business risk is mainly from users or systems opening untrusted image files.
Executive priority
Treat as a targeted exposure cleanup item, not an emergency, unless XnView 2.40 processes untrusted images in business workflows.
Technical view
The record describes a crafted .rle file affecting XnView Classic for Windows 2.40, related to faulting-address-controlled branch selection in GDI32!ScriptStringAnalyse. CVSS, CWE, and precise impact details are not provided in the source bundle.
Likely exposure
Exposure is likely limited to Windows endpoints or workflows using XnView Classic 2.40 to open or preview untrusted .rle files.
Exploitation context
The source bundle does not indicate CISA KEV listing or active exploitation. The described attack path appears file-based and requires processing a crafted .rle file.
Researcher notes
Evidence is sparse: no CVSS vector, CWE, patch reference, or confirmed exploitation appears in the bundle. Avoid assuming code execution; the record states denial of service or unspecified other impact.
Mitigation direction
- Inventory Windows endpoints for XnView Classic version 2.40.
- Check XnView vendor guidance for fixed versions or recommended handling.
- Restrict opening or previewing untrusted .rle files where feasible.
- Use endpoint controls to reduce user exposure to unsolicited image attachments.
- Monitor for repeated XnView crashes tied to RLE file handling.
Validation and detection
- Confirm whether XnView Classic 2.40 is installed in managed software inventory.
- Identify business workflows that receive or inspect .rle files.
- Review crash telemetry for XnView faults involving GDI32 ScriptStringAnalyse.
- Verify file-handling controls block unsolicited .rle content where required.
- Document compensating controls if upgrade status is unclear.
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-10766 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-10766CVE 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.