Security readout for executives and security teams
Plain-English summary
This is an old Windows desktop application flaw in XnView Classic 2.40. A malicious .rle image file could crash the application or potentially run code when processed. Business risk depends mainly on whether this legacy version is still installed and used to open untrusted image files.
Executive priority
Treat this as a targeted legacy-software cleanup item, not a broad emergency. Prioritize if XnView Classic 2.40 is present on user workstations that process external image files.
Technical view
The CVE describes arbitrary code execution or denial of service in XnView Classic for Windows 2.40 through a crafted .rle file, associated with a Data Execution Prevention violation. The public bundle does not include CVSS, CWE, root-cause detail, affected CPEs, or a named fixed version.
Likely exposure
Likely exposure is limited to Windows endpoints running XnView Classic 2.40, especially systems where users open downloaded, emailed, or shared .rle image files. Environments without this exact legacy application/version are not shown as affected by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or evidence of active exploitation. A public advisory reference exists, but the provided CVE data does not prove weaponized exploitation, broad campaign activity, or reliable exploit availability.
Researcher notes
Evidence is sparse. The CVE identifies product, version, file type, and impact class, but omits CVSS, CWE, exact vulnerable code path, fixed release, and exploit status. Avoid expanding scope beyond XnView Classic for Windows 2.40 without additional vendor evidence.
Mitigation direction
- Inventory Windows endpoints for XnView Classic 2.40.
- Remove XnView Classic where no business need exists.
- Check XnView or vendor guidance for supported fixed releases.
- Restrict untrusted .rle file handling where practical.
- Route suspicious image files through controlled analysis workflows.
Validation and detection
- Confirm whether XnView Classic 2.40 exists in software inventory.
- Verify file associations for .rle on affected Windows endpoints.
- Review endpoint telemetry for XnView crashes involving .rle files.
- Check email and web controls for risky image attachment handling.
- Document any compensating controls for retained legacy installs.
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-10739 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-10739CVE 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.