Security readout for executives and security teams
Plain-English summary
This CVE concerns XnView Classic for Windows 2.40 crashing, or possibly causing unspecified impact, when processing a crafted .rle image file. Business urgency depends on whether this legacy desktop software is still installed and used to open externally supplied image files.
Executive priority
Prioritize as a legacy desktop software hygiene issue unless the organization actively uses XnView Classic 2.40 with untrusted image files. Escalate remediation for teams that process external image submissions or attachments.
Technical view
The CVE description ties the issue to crafted .rle parsing in XnView Classic 2.40 for Windows, with fault data influencing branch selection in MSCTF!_CtfImeCreateThreadMgr. Public metadata provides no CVSS, CWE, CPE, confirmed patch, or detailed root cause.
Likely exposure
Exposure is likely limited to Windows endpoints running XnView Classic 2.40, especially where users open .rle files from email, downloads, archives, or third parties. The source bundle does not identify other affected versions or products.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, or public weaponization claims. The described attack requires a crafted .rle file to be processed by the vulnerable application.
Researcher notes
Evidence is sparse. The CVE record names XnView Classic 2.40 and .rle input, but omits CVSS, CWE, CPE, confirmed fix, and exploit maturity. Treat impact beyond denial of service as unconfirmed.
Mitigation direction
- Inventory Windows endpoints for XnView Classic 2.40.
- Check vendor or project guidance for fixed versions or advisories.
- Avoid opening untrusted .rle files in XnView Classic.
- Remove or replace the software where it is not business-required.
- Restrict .rle handling on managed endpoints where feasible.
Validation and detection
- Confirm whether XnView Classic 2.40 is installed on endpoints.
- Identify users or workflows that receive external .rle files.
- Review endpoint controls for file association and application launch paths.
- Check security telemetry for suspicious or unexpected .rle file handling.
- Do not test crafted files on production systems.
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-10773 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-10773CVE 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.