{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-17418 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-17418 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-17418 is a high-severity memory corruption vulnerability in Foxitsoftware Foxit Studio Photo, published on 9 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-17418 and fix it if it is affected.\n\nWhat it is: CVE-2020-17418 is a high-severity memory corruption vulnerability in Foxitsoftware Foxit Studio Photo, published on 9 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-17418 in the wild and no public exploit code.\n\nAffected product: Foxitsoftware Foxit Studio Photo. 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-2020-17418/ (Markdown: https://insights.sbomify.com/CVE-2020-17418/index.md)","id":"CVE-2020-17418","markdown":"https://insights.sbomify.com/CVE-2020-17418/index.md","name":"CVE-2020-17418","record":{"aliases":["GHSA-9mrp-7cm9-xqxq"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Foxit Studio Photo","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening malicious EZIX files in Foxit Studio Photo.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"foxit_studio_photo","vendor":"foxitsoftware"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit Studio Photo 3.6.6.922. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of EZIX files. A crafted id in a channel element can trigger a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-11197.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in Studio Photo","id":"CVE-2020-17418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"foxitsoftware:foxit_studio_photo","products":["foxitsoftware:foxit_studio_photo"],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Studio Photo","id":"CVE-2020-17419"},"packages":[],"prev":{"headline":"Use after free in Reader","id":"CVE-2020-17417"},"products":["Studio Photo"],"published":"2021-02-09","related":[{"cvss_score":7.8,"headline":"Memory corruption in Studio Photo","id":"CVE-2021-31433","kev_date_added":null,"published":"2021-04-29"},{"cvss_score":7.8,"headline":"Memory corruption in Studio Photo","id":"CVE-2021-31434","kev_date_added":null,"published":"2021-04-29"},{"cvss_score":7.8,"headline":"Memory corruption in Studio Photo","id":"CVE-2021-31435","kev_date_added":null,"published":"2021-04-29"},{"cvss_score":7.8,"headline":"Memory corruption in Studio Photo","id":"CVE-2021-31436","kev_date_added":null,"published":"2021-04-29"},{"cvss_score":7.8,"headline":"Memory corruption in Studio Photo","id":"CVE-2021-31437","kev_date_added":null,"published":"2021-04-29"},{"cvss_score":7.8,"headline":"Memory corruption in Studio Photo","id":"CVE-2021-31438","kev_date_added":null,"published":"2021-04-29"}],"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-04","vendors":["Foxit"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening malicious EZIX files in Foxit Studio Photo.","url":"https://insights.sbomify.com/CVE-2020-17418/"}