Security readout for executives and security teams
Plain-English summary
CVE-2017-9894 is a code execution vulnerability in XnView Classic for Windows 2.40 triggered by a crafted .fpx image file. Business risk depends on whether staff or automated workflows still use this old viewer and open FPX files from untrusted sources.
Executive priority
Treat as a targeted risk cleanup item. Prioritize if XnView Classic 2.40 is present on user workstations or file-processing systems, but do not claim active exploitation from the supplied evidence.
Technical view
The CVE describes a crafted FPX file causing a user-mode write access violation in Xfpx!gffGetFormatInfo. The public bundle identifies XnView Classic for Windows 2.40 and states remote attackers may execute code. No CVSS, CWE, vendor fix, or patch version is provided.
Likely exposure
Exposure appears limited to Windows systems running XnView Classic 2.40, especially where users preview, open, or process untrusted .fpx files.
Exploitation context
The bundle does not cite CISA KEV listing or active exploitation. The described attack path requires a malicious FPX file to be opened or processed by the vulnerable application.
Researcher notes
Evidence is sparse. The key technical artifact is a user-mode write access violation in Xfpx!gffGetFormatInfo associated with FPX parsing. The bundle does not provide root cause analysis, exploit reliability, affected CPEs, or remediation details.
Mitigation direction
- Inventory endpoints for XnView Classic for Windows 2.40.
- Check XnView vendor guidance for fixed versions or supported upgrade paths.
- Restrict opening FPX files from email, web downloads, and external media.
- Remove the vulnerable application where there is no business need.
- Prefer supported image viewers for untrusted image handling.
Validation and detection
- Confirm installed XnView Classic versions on Windows endpoints.
- Check file associations and workflows that process .fpx files.
- Review email and web controls for FPX attachment handling.
- Look for recent untrusted FPX files opened on affected systems.
- Track vendor or CVE updates for remediation details.
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-9894 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-9894CVE 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.