Security readout for executives and security teams
Plain-English summary
This CVE concerns XnView Classic for Windows 2.40. A specially crafted .rle image file may crash the application and may have other unspecified impact. The public record does not provide a CVSS score, confirmed patch, or evidence of active exploitation.
Executive priority
Treat this as a targeted legacy desktop-file risk, not a broadly exposed internet service issue. Prioritize environments with XnView Classic 2.40 and users who handle external image files.
Technical view
The CVE describes malformed .rle processing leading to control over branch selection during Windows heap free-block coalescing in ntdll. Reported impact is denial of service or unspecified other impact. Available sources do not define a CWE, affected range beyond version 2.40, or a confirmed exploit status.
Likely exposure
Exposure appears limited to Windows systems running XnView Classic 2.40 where users can open untrusted .rle files. The source bundle does not identify broader product versions, server-side exposure, or network-reachable attack surface.
Exploitation context
The record describes a crafted-file attack. KEV is false, and the provided sources do not state active exploitation. The practical risk depends on whether targeted users receive and open untrusted .rle files in the affected application.
Researcher notes
Evidence is sparse: no CVSS, CWE, vendor fix, or affected-version range beyond XnView Classic for Windows 2.40 is provided. The GitHub advisory is the main technical reference, and the CVE text only states denial of service or unspecified impact.
Mitigation direction
- Inventory Windows endpoints for XnView Classic version 2.40.
- Check XnView or vendor guidance for fixed versions or retirement advice.
- Restrict opening untrusted .rle files in XnView Classic.
- Consider removing file associations for .rle where business use is unnecessary.
- Use endpoint controls to quarantine suspicious image attachments.
Validation and detection
- Confirm installed XnView Classic versions on managed Windows assets.
- Review whether .rle files are used in normal business workflows.
- Check endpoint logs for XnView crashes involving .rle files.
- Verify whether users can receive .rle files through email or collaboration tools.
- Document any compensating controls for untrusted file handling.
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-10757 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-10757CVE 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.