Security readout for executives and security teams
Plain-English summary
This issue affects XnView Classic for Windows 2.40 when handling a crafted .rle image file. If a user opens a malicious file, the application may crash or potentially allow code execution. The source bundle does not provide CVSS scoring, confirmed exploitation, or a named vendor patch.
Executive priority
Treat as a targeted endpoint risk, not a broad infrastructure emergency. Prioritize teams that process externally supplied images, especially where legacy XnView Classic 2.40 remains installed.
Technical view
CVE-2017-10738 describes arbitrary code execution or denial of service in XnView Classic 2.40 for Windows via a crafted .rle file. The reported symptom is a Data Execution Prevention violation involving CompareStringW. No CWE, CVSS vector, exploit status, or remediation details are included in the provided sources.
Likely exposure
Exposure is likely limited to endpoints where XnView Classic 2.40 for Windows is installed and users can open untrusted .rle files. Server-side exposure is not indicated by the provided sources.
Exploitation context
The sources support a malicious-file scenario requiring a crafted .rle file to be processed by the affected application. CISA KEV status is false in the bundle, and no cited source confirms active exploitation.
Researcher notes
Evidence is sparse: the CVE description and referenced advisory identify .rle parsing as the trigger, but the bundle lacks crash artifacts, root-cause detail, affected-version range, CVSS, CWE, and remediation confirmation.
Mitigation direction
- Identify systems running XnView Classic 2.40 for Windows.
- Check XnView vendor guidance for fixed versions or recommended remediation.
- Restrict opening .rle files from email, web downloads, or unknown sources.
- Use safer image viewers for untrusted or externally supplied files.
- Consider removing XnView Classic 2.40 where it is not business-required.
Validation and detection
- Inventory installed XnView Classic versions on managed Windows endpoints.
- Review file-association policies for .rle files on affected systems.
- Check security controls for blocking suspicious image attachments.
- Confirm users handling external images are not using version 2.40.
- Track whether vendor guidance documents a fixed release.
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-10738 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-10738CVE 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.