{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5837 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-5837 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-5837 is a high-severity path traversal vulnerability in Symantec Endpoint Protection, published on 11 May 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5837 and fix it if it is affected.\n\nWhat it is: CVE-2020-5837 is a high-severity path traversal vulnerability in Symantec Endpoint Protection, published on 11 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5837 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-2020-5837/ (Markdown: https://insights.sbomify.com/CVE-2020-5837/index.md)","id":"CVE-2020-5837","markdown":"https://insights.sbomify.com/CVE-2020-5837/index.md","name":"CVE-2020-5837","record":{"aliases":["GHSA-qfhx-mfmg-3wfg"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Endpoint Protection","requires_auth":"low_privilege","summary":"Attackers can exploit symbolic link handling in log files to achieve privilege escalation in Symantec Endpoint Protection.","user_interaction":"not_required","vuln_class":"path_traversal"},"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.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Symantec Endpoint Protection, prior to 14.3, may not respect file permissions when writing to log files that are replaced by symbolic links, which can lead to a potential elevation of privilege.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-04-16","github_poc":1,"max_poc_stars":39,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-04-16T08:15:18Z","kind":"github_poc","ref":"https://github.com/RedyOpsResearchLabs/SEP-14.2-Arbitrary-Write","stars":39,"title":"CVE-2020-5837 exploit"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Path traversal in Symantec Endpoint Protection","id":"CVE-2020-5837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"symantec:endpoint_protection","products":["symantec:endpoint_protection"],"type":"path_traversal","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in IT Analytics","id":"CVE-2020-5838"},"packages":[],"prev":{"headline":"Privilege escalation in Symantec Endpoint Protection","id":"CVE-2020-5836"},"products":["Symantec Endpoint Protection"],"published":"2020-05-11","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":"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can exploit symbolic link handling in log files to achieve privilege escalation in Symantec Endpoint Protection.","url":"https://insights.sbomify.com/CVE-2020-5837/"}