{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-9146 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-9146 is a high-severity memory corruption vulnerability in n/a, published on 22 May 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-9146 and fix it if it is affected.\n\nWhat it is: CVE-2017-9146 is a high-severity memory corruption vulnerability in n/a, published on 22 May 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-9146 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-9146/ (Markdown: https://insights.sbomify.com/CVE-2017-9146/index.md)","id":"CVE-2017-9146","markdown":"https://insights.sbomify.com/CVE-2017-9146/index.md","name":"CVE-2017-9146","record":{"aliases":["DEBIAN-CVE-2017-9146","GHSA-798c-jx77-ccgp","UBUNTU-CVE-2017-9146"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ytnef library","requires_auth":"none","summary":"Remote attackers can cause denial of service or potential code execution via a crafted TNEF file due to improper memory allocation handling in the ytnef library.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ytnef","vendor":"ytnef_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"The TNEFFillMapi function in lib/ytnef.c in libytnef in ytnef through 1.9.2 does not ensure a nonzero count value before a certain memory allocation, which allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted tnef file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2017-9146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-9147"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-9145"},"products":["n/a"],"published":"2017-05-22","related":[{"cvss_score":9.8,"headline":"ytnef has directory traversal","id":"CVE-2009-3887","kev_date_added":null,"published":"2019-10-29"},{"cvss_score":5.5,"headline":"Memory corruption in n/a","id":"CVE-2017-12141","kev_date_added":null,"published":"2017-08-02"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2017-12142","kev_date_added":null,"published":"2017-08-02"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2017-12144","kev_date_added":null,"published":"2017-08-02"},{"cvss_score":5.5,"headline":"Null dereference in n/a","id":"CVE-2017-9470","kev_date_added":null,"published":"2017-06-07"},{"cvss_score":5.5,"headline":"Memory corruption in n/a","id":"CVE-2017-9472","kev_date_added":null,"published":"2017-06-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service or potential code execution via a crafted TNEF file due to improper memory allocation handling in the ytnef library.","url":"https://insights.sbomify.com/CVE-2017-9146/"}