Security readout for executives and security teams
Plain-English summary
This issue affects XnView Classic for Windows 2.40 when handling specially crafted RLE image files. A user opening a malicious .rle file could experience application crash or possible code execution. The provided sources do not give CVSS, confirmed patch details, or evidence of active exploitation.
Executive priority
Treat as targeted cleanup unless XnView Classic 2.40 is broadly deployed or used with untrusted image files. The potential impact is serious, but public evidence in the bundle is sparse.
Technical view
CVE-2017-10749 describes a crafted .rle parsing flaw in XnView Classic for Windows 2.40, associated with a user-mode write access violation near NULL under WOW64. Reported impact is arbitrary code execution or denial of service, but the source bundle lacks CWE, CPE, CVSS, and remediation detail.
Likely exposure
Exposure is likely limited to Windows endpoints running XnView Classic 2.40, especially where users can open untrusted .rle files from email, downloads, shares, or archives.
Exploitation context
The sources support a crafted-file attack scenario requiring the vulnerable application to process a malicious RLE file. CISA KEV is false in the bundle, and no cited source confirms active exploitation.
Researcher notes
The record is thin: no CVSS, CWE, CPE, or named fix is provided. Analysis should focus on confirming exact product/version exposure and obtaining vendor advisory or changelog evidence before assigning operational severity.
Mitigation direction
- Inventory endpoints for XnView Classic for Windows 2.40.
- Check XnView vendor guidance for fixed versions or replacement recommendations.
- Restrict opening untrusted .rle files until remediation is confirmed.
- Remove or upgrade legacy XnView Classic installations where business use is not required.
- Use endpoint controls to quarantine suspicious RLE attachments or downloads.
Validation and detection
- Confirm whether XnView Classic 2.40 is installed on managed Windows systems.
- Review software inventory for other untracked portable XnView Classic copies.
- Check file association policies for .rle files on affected endpoints.
- Review email and web controls for RLE file handling.
- Verify remediation against vendor release notes or official guidance.
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-10749 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-10749CVE 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.