Security readout for executives and security teams
Plain-English summary
CVE-2017-9470 is a crash bug in ytnef 1.9.2. A specially crafted file can make the application dereference a NULL pointer and crash. The cited sources describe denial of service only, not code execution or data theft.
Executive priority
Address during routine patching unless ytnef processes external email attachments in a critical workflow. In that case, prioritize validation and vendor package updates because a crafted file could interrupt service availability.
Technical view
The issue is in MAPIPrint in lib/ytnef.c in ytnef 1.9.2. Processing a crafted file can trigger a NULL pointer dereference, causing application termination. The source bundle provides no CVSS score, CWE, CPE list, or exact fixed version.
Likely exposure
Exposure is most likely where ytnef 1.9.2 processes untrusted TNEF or email attachment files. The source bundle does not enumerate affected CPEs or downstream products, so confirm installed package versions through asset inventory and distribution advisories.
Exploitation context
The CVE describes remote attackers causing denial of service with a crafted file. CISA KEV status is false in the bundle, and no cited source states active exploitation. Treat exploitation evidence as incomplete.
Researcher notes
The record is sparse: no CVSS, CWE, CPEs, or fixed version are provided in the bundle. The reliable claim is NULL pointer dereference in MAPIPrint causing application crash via crafted file in ytnef 1.9.2.
Mitigation direction
- Identify systems running ytnef, especially version 1.9.2.
- Check Fedora, Gentoo, and vendor package guidance for corrected ytnef builds.
- Avoid processing untrusted crafted TNEF files with affected versions.
- Constrain attachment parsing so crashes do not disrupt critical services.
Validation and detection
- Confirm ytnef package versions across servers, containers, and mail-processing workers.
- Review mail or file-processing paths that invoke ytnef on untrusted input.
- Check vendor advisories for whether installed builds include the fix.
- Verify crash isolation and monitoring for attachment parsing components.
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-9470 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://blogs.gentoo.org/ago/2017/05/24/ytnef-null-pointer-dereference-in-mapiprint-ytnef-c/CVE reference · x_refsource_MISC
- FEDORA-2019-7d7083b8beCVE reference · vendor-advisory, x_refsource_FEDORA
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.