Security readout for executives and security teams
Plain-English summary
CVE-2017-9912 is a file-parsing issue in XnView Classic for Windows 2.40. A malicious FPX image file can crash the application and may have other unspecified impact. Public sources do not provide a severity score, patch version, or evidence of active exploitation.
Executive priority
Treat this as a targeted legacy software risk, not a broad emergency. Prioritize if the application remains installed in environments that receive untrusted image files.
Technical view
The CVE describes crafted .fpx input influencing heap-control flow during RtlpFreeHeap, causing denial of service and possibly unspecified additional impact. The only named affected product/version in the bundle is XnView Classic for Windows 2.40. No CWE, CVSS, fixed release, or exploit-in-the-wild evidence is provided.
Likely exposure
Exposure is likely limited to Windows systems running XnView Classic 2.40 where users can open or preview FPX files from untrusted sources. The source bundle does not identify other affected versions or products.
Exploitation context
The record is not listed in KEV, and the provided sources do not claim active exploitation. The attack scenario is malicious file handling, requiring the vulnerable application to process a crafted FPX file.
Researcher notes
Evidence is sparse. The CVE names FPX parsing and heap-related control-flow behavior, but does not prove code execution, name a fix, or define affected version ranges beyond XnView Classic 2.40.
Mitigation direction
- Inventory Windows endpoints for XnView Classic 2.40.
- Check XnView vendor guidance for fixed versions or retirement advice.
- Restrict opening FPX files from email, downloads, and untrusted shares.
- Remove or replace unsupported vulnerable installations where practical.
- Use endpoint controls to limit untrusted file associations.
Validation and detection
- Confirm whether XnView Classic 2.40 exists in software inventory.
- Review file associations for .fpx on managed Windows endpoints.
- Check crash telemetry for XnView failures involving FPX files.
- Verify users handling untrusted images do not use vulnerable builds.
- Document any compensating controls for legacy installations.
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-9912 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-9912CVE 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.