Security readout for executives and security teams
Plain-English summary
CVE-2017-9893 affects XnView Classic for Windows 2.40. A malicious FPX image file can trigger code execution when processed by the application. Business risk depends on whether this legacy Windows viewer is installed and allowed to open untrusted image attachments or downloads.
Executive priority
Prioritize if XnView Classic 2.40 is present on business endpoints or used to process external image files. If absent, treat as a low operational concern after confirming inventory.
Technical view
The CVE describes remote code execution through a crafted .fpx file in XnView Classic 2.40, tied to a user-mode write access violation in Xfpx!gffGetFormatInfo. The sources do not provide CVSS, CWE, affected CPEs, patch details, or a confirmed fixed version.
Likely exposure
Exposure is likely limited to Windows systems running XnView Classic 2.40, especially endpoints where users preview or open FPX files from email, web downloads, shared drives, or customer submissions.
Exploitation context
CISA KEV is false in the provided bundle, and the cited sources do not claim active exploitation. The public GitHub advisory indicates enough technical detail exists to understand the crash condition, but this assessment should not be treated as proof of exploitation in the wild.
Researcher notes
Evidence is sparse. The CVE states RCE via crafted FPX and names an access violation location, but does not include CVSS, CWE, affected CPEs, patch status, or exploit-in-the-wild confirmation. Validation should focus on product presence, version, and FPX exposure paths.
Mitigation direction
- Inventory Windows endpoints for XnView Classic 2.40.
- Check XnView vendor guidance for fixed or supported versions.
- Remove or upgrade unsupported XnView Classic installations where feasible.
- Block or quarantine untrusted .fpx files at email and web controls.
- Limit FPX file association with XnView Classic on managed endpoints.
Validation and detection
- Confirm whether XnView Classic 2.40 exists in software inventory.
- Review endpoint file associations for .fpx handling.
- Check mail and web gateways for FPX attachment controls.
- Verify users handling untrusted images are not using affected versions.
- Document compensating controls if no vendor fix is confirmed.
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-9893 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-9893CVE 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.