{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-5237 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-5237 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-5237 is a high-severity vulnerability in Symantec Endpoint Protection, published on 20 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-5237 and fix it if it is affected.\n\nWhat it is: CVE-2018-5237 is a high-severity vulnerability in Symantec Endpoint Protection, published on 20 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-5237 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-2018-5237/ (Markdown: https://insights.sbomify.com/CVE-2018-5237/index.md)","id":"CVE-2018-5237","markdown":"https://insights.sbomify.com/CVE-2018-5237/index.md","name":"CVE-2018-5237","record":{"aliases":["GHSA-jfhh-fgpm-vwh3"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Endpoint Protection","requires_auth":"low_privilege","summary":"Attackers can gain elevated access to protected resources in Symantec Endpoint Protection, requiring an upgrade to mitigate.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"endpoint_protection","vendor":"symantec"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Symantec Endpoint Protection prior to 14 RU1 MP1 or 12.1 RU6 MP10 could be susceptible to a privilege escalation vulnerability, which is a type of issue that allows a user to gain elevated access to resources that are normally protected at lower access levels.","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":"Privilege escalation in Symantec Endpoint Protection","id":"CVE-2018-5237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"symantec:endpoint_protection","products":["symantec:endpoint_protection"],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Other in Norton Power Eraser","id":"CVE-2018-5238"},"packages":[],"prev":{"headline":"Race condition in Symantec Endpoint Protection","id":"CVE-2018-5236"},"products":["Symantec Endpoint Protection"],"published":"2018-06-20","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":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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Symantec Corporation"]},"summary":"Attackers can gain elevated access to protected resources in Symantec Endpoint Protection, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2018-5237/"}