Security readout for executives and security teams
Plain-English summary
This CVE concerns XnView Classic for Windows 2.40 handling a specially crafted RLE image file. The public record supports denial of service and mentions possible unspecified impact, but does not provide severity, CVSS, CWE, or a named fix.
Executive priority
Treat this as a targeted endpoint hygiene issue, not an emergency, unless affected systems routinely process untrusted image files.
Technical view
The CVE describes a crafted .rle file affecting XnView Classic for Windows 2.40. The issue is related to faulting-address data controlling branch selection at COMCTL32!SetStatusText+0x29. Public details indicate denial of service or unspecified other impact, with no CVSS, CWE, or confirmed remediation in the provided sources.
Likely exposure
Exposure is likely limited to Windows endpoints running XnView Classic 2.40, especially where users open externally supplied or untrusted .rle image files.
Exploitation context
The source bundle does not show KEV listing, active exploitation, public weaponization, or remote network exploitation. Evidence supports a crafted-file attack surface only.
Researcher notes
The record is sparse: affected CPEs are n/a, no CVSS or CWE is supplied, and no fixed version is named. Validate exposure from software inventory and preserve uncertainty around impact beyond denial of service.
Mitigation direction
- Inventory XnView Classic installations and identify Windows Version 2.40.
- Check XnView or vendor guidance for fixed builds before approving continued use.
- Restrict opening untrusted .rle files until systems are updated or risk-accepted.
- Prefer supported image viewers for workflows that process external files.
Validation and detection
- Confirm whether XnView Classic for Windows 2.40 exists on managed endpoints.
- Review file-handling workflows for externally supplied .rle content.
- Verify endpoint controls can flag suspicious RLE attachments or downloads.
- Document any exception where affected software remains installed.
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-10760 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-10760CVE 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.