Security readout for executives and security teams
Plain-English summary
This issue affects XnView Classic for Windows 2.40 when processing a crafted .rle image file. The public record says it may crash the application and may have other unspecified impact. The available sources do not provide a CVSS score, confirmed fix, or active exploitation evidence.
Executive priority
Prioritize as a legacy endpoint hygiene issue, not as a confirmed internet-wide emergency. Escalate remediation where external image files are handled or where the affected viewer remains installed on sensitive workstations.
Technical view
CVE-2017-10779 describes crafted RLE input influencing branch selection in XnView Classic 2.40, with the CVE text citing control from data at the faulting address near xnview+0x13a20. Public details identify denial of service and unspecified other impact, but do not document exploitability, root cause class, or remediation version.
Likely exposure
Exposure is most likely on Windows systems still running XnView Classic 2.40, especially where users open RLE files from email, downloads, shared folders, or customer submissions. The source bundle does not identify other affected versions or products.
Exploitation context
The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The known attack condition is user or workflow processing of a crafted .rle file in the affected application.
Researcher notes
Public evidence is thin: no CVSS, CWE, affected CPEs, patch reference, or confirmed exploitation is provided in the bundle. Analysis should stay limited to XnView Classic for Windows 2.40 and crafted .rle file handling unless additional vendor or researcher sources are reviewed.
Mitigation direction
- Inventory and retire XnView Classic 2.40 where it is not business-critical.
- Check XnView vendor guidance for fixed versions or supported migration options.
- Avoid opening untrusted .rle files with the affected application.
- Restrict RLE file associations on systems exposed to external files.
- Use sandboxing or isolation for legacy image-processing workflows.
Validation and detection
- Confirm whether XnView Classic 2.40 exists on managed Windows endpoints.
- Identify workflows that process RLE files from untrusted sources.
- Check whether users can open .rle attachments or downloads by default.
- Review vendor guidance before declaring remediation complete.
- Document compensating controls if the application cannot be removed.
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-10779 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-10779CVE 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.