Security readout for executives and security teams
Plain-English summary
This CVE affects XnView Classic for Windows 2.40 when handling crafted RLE image files. A malicious file could crash the application or potentially run code. Business risk is mainly on workstations where users open images from email, downloads, tickets, or shared folders.
Executive priority
Treat as targeted workstation risk rather than internet-facing emergency. Prioritize environments where image files from outsiders are routinely handled, such as support, design, research, or intake workflows.
Technical view
The record describes arbitrary code execution or denial of service via a crafted .rle file, tied to a Data Execution Prevention violation during loader initialization. The source bundle gives no CVSS, CWE, confirmed patch, or detailed affected CPE data beyond XnView Classic for Windows 2.40.
Likely exposure
Exposure is likely limited to Windows systems with XnView Classic 2.40 installed, especially where .rle files are opened from untrusted sources or associated with XnView by default.
Exploitation context
No KEV listing or cited source in the bundle indicates active exploitation. The public advisory reference suggests the issue was publicly disclosed, but the bundle does not provide exploit maturity, weaponization status, or field telemetry.
Researcher notes
Evidence is sparse. The CVE description identifies crafted RLE parsing leading to DEP violation, arbitrary code execution, or DoS, but does not include root cause, affected library details, CVSS, CWE, or confirmed fix information.
Mitigation direction
- Inventory endpoints for XnView Classic for Windows 2.40.
- Check XnView vendor guidance for fixed or supported versions.
- Limit opening .rle files from email, web downloads, and shared folders.
- Remove risky file associations where XnView is not required.
- Use endpoint controls to contain untrusted image processing.
Validation and detection
- Confirm installed XnView Classic versions on Windows endpoints.
- Review default handlers for .rle files.
- Check whether users receive or process RLE image files.
- Look for crash reports involving XnView and RLE files.
- Verify remediation against vendor guidance once identified.
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-10742 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-10742CVE 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.