{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2018-18369 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18369 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18369 is a high-severity vulnerability in Symantec Endpoint Protection, published on 25 Apr 2019. 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-2018-18369 and fix it if it is affected.\n\nWhat it is: CVE-2018-18369 is a high-severity vulnerability in Symantec Endpoint Protection, published on 25 Apr 2019. 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-2018-18369 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-18369/ (Markdown: https://insights.sbomify.com/CVE-2018-18369/index.md)","id":"CVE-2018-18369","markdown":"https://insights.sbomify.com/CVE-2018-18369/index.md","name":"CVE-2018-18369","record":{"aliases":["GHSA-cqr9-3mc7-gvpr"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Norton Security client","requires_auth":"none","summary":"Attackers can execute arbitrary code by placing a malicious DLL in a location searched by the application before the legitimate one.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"endpoint_protection","vendor":"symantec"},{"product":"endpoint_protection_cloud","vendor":"symantec"},{"product":"endpoint_protection_cloud_agent","vendor":"symantec"},{"product":"norton_security","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-426","name":"Untrusted Search Path"}],"description":"Norton Security (Windows client) prior to 22.16.3 and SEP SBE (Windows client) prior to Cloud Agent 3.00.31.2817, NIS-22.15.2.22 \u0026 SEP-12.1.7484.7002, may be susceptible to a DLL Preloading vulnerability, which is a type of issue that can occur when an application looks to call a DLL for execution and an attacker provides a malicious DLL to use instead.","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":"Other in Norton Security","id":"CVE-2018-18369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"symantec:endpoint_protection","products":["symantec:endpoint_protection"],"type":"other","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Symantec Advanced Secure Gateway (ASG)","id":"CVE-2018-18370"},"packages":[],"prev":{"headline":"Privilege escalation in Symantec Endpoint Protection Manager (SEPM)","id":"CVE-2018-18368"},"products":["Norton Security","Symantec Endpoint Protection Small Business Edition"],"published":"2019-04-25","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-08-05","vendors":["Symantec Corporation"]},"summary":"Attackers can execute arbitrary code by placing a malicious DLL in a location searched by the application before the legitimate one.","url":"https://insights.sbomify.com/CVE-2018-18369/"}