Security readout for executives and security teams
Plain-English summary
This issue affects XnView Classic for Windows 2.40 when it processes a malicious FPX image file. The public record says attackers could execute code through a crafted file. Business risk is highest where users open image files from email, web downloads, customer submissions, or shared drives.
Executive priority
Prioritize remediation if XnView Classic 2.40 is present in environments that handle external image files. The business urgency comes from potential code execution, but the evidence base is sparse and does not prove active exploitation.
Technical view
CVE-2017-9902 describes a code execution flaw in XnView Classic for Windows 2.40 via crafted .fpx input. The CVE notes faulting-address data controlling code flow in Xfpx!gffGetFormatInfo. No CVSS, CWE, CPE, patch, or vendor mitigation is included in the supplied sources.
Likely exposure
Likely exposure is limited to Windows systems running XnView Classic 2.40, especially if .fpx files are accepted from untrusted sources or associated with XnView. The supplied affected-product metadata is incomplete, so confirm locally before scoping broader exposure.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The plausible attack path is user or workflow processing of a crafted FPX file in the vulnerable application. No exploit maturity or public weaponization status is established by the supplied sources.
Researcher notes
The advisory record is minimal. Key gaps are absent CVSS, absent CPEs, no named fixed version, no CWE, and no confirmed exploitation evidence. Treat the RCE description seriously, but base exposure decisions on actual software inventory and FPX handling paths.
Mitigation direction
- Inventory Windows endpoints for XnView Classic 2.40.
- Check XnView vendor guidance for fixed versions or supported upgrade paths.
- Restrict or quarantine .fpx files from untrusted sources.
- Remove risky file associations where XnView opens FPX files automatically.
- Use least-privilege accounts for users handling external image files.
Validation and detection
- Confirm installed XnView Classic versions on Windows endpoints.
- Check whether .fpx files are associated with XnView Classic.
- Review email and web controls for FPX attachment handling.
- Search security logs for unusual FPX file handling events.
- Verify remediation against vendor guidance, not assumptions.
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-9902 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-9902CVE 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.