Security readout for executives and security teams
Plain-English summary
A malicious RLE image file can crash XnView Classic 2.40 for Windows and may allow code execution when opened. The risk is mainly to workstations where users process untrusted image files. Public data does not include CVSS, named fixes, or confirmed exploitation.
Executive priority
Prioritize remediation where XnView is used on employee workstations that handle external image files. Treat this as high risk because code execution is possible, but scope may be narrow and exploitation evidence is not shown.
Technical view
The CVE describes arbitrary code execution or denial of service through a crafted .rle file, linked to a user-mode write access violation in msvcrt!_VEC_memzero. The source bundle identifies XnView Classic for Windows 2.40, but lacks CWE, CPE, CVSS, and remediation detail.
Likely exposure
Exposure is likely limited to Windows systems with XnView Classic 2.40 installed, especially where users open RLE files from email, downloads, archives, or shared drives.
Exploitation context
The known attack path is file-based: a crafted .rle file must be opened or processed by the vulnerable application. The CVE is not listed in KEV, and the provided sources do not claim active exploitation.
Researcher notes
Evidence is sparse. The CVE and advisory identify the vulnerable version, file type, and crash context, but do not provide CVSS, CWE, CPE, exploit status, or a named patch. Avoid assuming broader XnView product impact without vendor confirmation.
Mitigation direction
- Inventory systems for XnView Classic for Windows 2.40.
- Check XnView vendor guidance for fixed versions or supported upgrade paths.
- Restrict opening RLE files from untrusted sources.
- Filter or quarantine unexpected .rle attachments and downloads.
- Use endpoint controls to limit vulnerable app execution where possible.
Validation and detection
- Confirm whether XnView Classic 2.40 is installed on managed Windows endpoints.
- Review file-handling workflows for RLE images from external sources.
- Check endpoint telemetry for crashes involving XnView and msvcrt write access violations.
- Verify whether vendor-supported versions are deployed after remediation.
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-10736 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-10736CVE 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.