{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-9094 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-9094 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-9094 is a high-severity code injection vulnerability in Symantec Endpoint Protection, published on 16 Apr 2018. 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-2016-9094 and fix it if it is affected.\n\nWhat it is: CVE-2016-9094 is a high-severity code injection vulnerability in Symantec Endpoint Protection, published on 16 Apr 2018. 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-2016-9094 in the wild and no public exploit code.\n\nAffected product: Symantec Endpoint Protection. 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-2016-9094/ (Markdown: https://insights.sbomify.com/CVE-2016-9094/index.md)","id":"CVE-2016-9094","markdown":"https://insights.sbomify.com/CVE-2016-9094/index.md","name":"CVE-2016-9094","record":{"aliases":["GHSA-cgj4-g3hw-mr32"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Endpoint Protection","requires_auth":"none","summary":"Attackers can execute arbitrary code via CSV formula injection in Symantec Endpoint Protection quarantine logs when users export and open them.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"endpoint_protection","vendor":"symantec"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","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-20","name":"Improper Input Validation"}],"description":"Symantec Endpoint Protection clients place detected malware in quarantine as part of the intended product functionality. The quarantine logs can be exported for review by the user in a variety of formats including .CSV files. Prior to 14.0 MP1 and 12.1 RU6 MP7, the potential exists for file metadata to be interpreted and evaluated as a formula. Successful exploitation of an attack of this type requires considerable direct user-interaction from the user exporting and then opening the log files on the intended target client.","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":"Code injection in Endpoint Protection","id":"CVE-2016-9094","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"symantec:endpoint_protection","products":["symantec:endpoint_protection"],"type":"code_injection","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-9095"},"packages":[],"prev":{"headline":"Privilege escalation in Endpoint Protection","id":"CVE-2016-9093"},"products":["Endpoint Protection"],"published":"2018-04-16","related":[{"cvss_score":9.3,"headline":"Code injection in n/a","id":"CVE-2012-0295","kev_date_added":null,"published":"2012-05-23"},{"cvss_score":8.8,"headline":"Privilege escalation in Symantec Endpoint Protection","id":"CVE-2018-5237","kev_date_added":null,"published":"2018-06-20"},{"cvss_score":7.8,"headline":"Privilege escalation in Symantec Endpoint Protection","id":"CVE-2020-5836","kev_date_added":null,"published":"2020-05-11"},{"cvss_score":7.8,"headline":"Path traversal in Symantec Endpoint Protection","id":"CVE-2020-5837","kev_date_added":null,"published":"2020-05-11"},{"cvss_score":7.8,"headline":"Privilege escalation in Symantec Endpoint Protection (SEP) and Symantec Endpoint Protection Small Business Edition (SEP SBE)","id":"CVE-2020-5820","kev_date_added":null,"published":"2020-02-11"},{"cvss_score":7.8,"headline":"Code injection in Symantec Endpoint Protection (SEP) and Symantec Endpoint Protection Small Business Edition (SEP SBE)","id":"CVE-2020-5821","kev_date_added":null,"published":"2020-02-11"},{"cvss_score":7.8,"headline":"Privilege escalation in Symantec Endpoint Protection (SEP) and Symantec Endpoint Protection Small Business Edition (SEP SBE)","id":"CVE-2020-5822","kev_date_added":null,"published":"2020-02-11"}],"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-09-16","vendors":["Symantec Corporation"]},"summary":"Attackers can execute arbitrary code via CSV formula injection in Symantec Endpoint Protection quarantine logs when users export and open them.","url":"https://insights.sbomify.com/CVE-2016-9094/"}