Security readout for executives and security teams
Plain-English summary
This CVE concerns XnView Classic for Windows 2.40 processing a crafted .rle image file. The public record says it may cause a denial of service and possibly other unspecified impact. The available bundle does not provide a CVSS score, confirmed patch, or evidence of active exploitation.
Executive priority
Treat this as a targeted hygiene issue unless XnView Classic 2.40 is widely deployed or used to handle external image files. Prioritize inventory and restriction first, because public evidence does not establish active exploitation or a confirmed fix.
Technical view
The issue is tied to crafted RLE file handling in XnView Classic 2.40, with the CVE description referencing attacker-controlled data influencing branch selection at ntdll memcmp during RPC initialization. Public details are sparse and do not define the memory-safety root cause or reliable impact beyond denial of service.
Likely exposure
Exposure is most likely on Windows endpoints that still have XnView Classic 2.40 installed and can open untrusted .rle files. The source bundle does not provide CPEs, affected version ranges beyond 2.40, or deployment prevalence.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. The described attack path appears to require a crafted .rle file being opened or processed by the affected application.
Researcher notes
The public record is thin: no CVSS, CWE, CPE, patch status, or detailed root-cause analysis is included. Avoid assuming code execution. Focus research on confirming affected binaries, crash conditions, vendor advisories, and whether later XnView Classic releases address the RLE handling flaw.
Mitigation direction
- Inventory Windows systems for XnView Classic 2.40 installations.
- Check XnView/vendor guidance for a supported fixed version or advisory.
- Restrict opening untrusted .rle files with XnView Classic 2.40.
- Remove or restrict the application where it is not business-required.
- Use endpoint controls to limit risky file associations if vendor guidance is unavailable.
Validation and detection
- Confirm installed XnView Classic versions on managed Windows endpoints.
- Identify whether .rle files are associated with XnView Classic.
- Review endpoint crash telemetry for XnView failures involving RLE files.
- Check mail and web controls for recent .rle file delivery to users.
- Record whether vendor documentation identifies a patch or workaround.
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-10772 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-10772CVE 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.