{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-0597 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-0597 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-0597 is a high-severity vulnerability in Microsoft Visual Studio Code, published on 26 Jun 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-2018-0597 and fix it if it is affected.\n\nWhat it is: CVE-2018-0597 is a high-severity vulnerability in Microsoft Visual Studio Code, published on 26 Jun 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-2018-0597 in the wild and no public exploit code.\n\nAffected product: Microsoft Visual Studio Code. 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-0597/ (Markdown: https://insights.sbomify.com/CVE-2018-0597/index.md)","id":"CVE-2018-0597","markdown":"https://insights.sbomify.com/CVE-2018-0597/index.md","name":"CVE-2018-0597","record":{"aliases":["GHSA-fjwh-37m4-wmr4"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VS Code installer","requires_auth":"none","summary":"An attacker can gain privileges via a Trojan horse DLL in the Visual Studio Code installer due to an untrusted search path vulnerability.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"visual_studio_code","vendor":"microsoft"}],"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":"Untrusted search path vulnerability in the installer of Visual Studio Code allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.","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 The installer of Visual Studio Code","id":"CVE-2018-0597","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio_code","products":["microsoft:visual_studio_code"],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in Self-extracting archive files created by IExpress bundled with Microsoft Windows","id":"CVE-2018-0598"},"packages":[],"prev":{"headline":"Privilege escalation in The installer of Visual Studio Community","id":"CVE-2018-0596"},"products":["The installer of Visual Studio Code"],"published":"2018-06-26","related":[{"cvss_score":9.6,"headline":"Visual Studio Code Security Feature Bypass Vulnerability","id":"CVE-2026-81376","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":9.6,"headline":"Visual Studio Code Elevation of Privilege Vulnerability","id":"CVE-2026-47281","kev_date_added":null,"published":"2026-06-09"},{"cvss_score":8.8,"headline":"Visual Studio Code Security Feature Bypass Vulnerability","id":"CVE-2026-78462","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":8.8,"headline":"Visual Studio Code Remote Code Execution Vulnerability","id":"CVE-2026-59113","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":8.8,"headline":"Visual Studio Code Remote Code Execution Vulnerability","id":"CVE-2026-69320","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":8.8,"headline":"Visual Studio Code Remote Code Execution Vulnerability","id":"CVE-2026-70336","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":8.8,"headline":"Visual Studio Code Security Feature Bypass Vulnerability","id":"CVE-2026-57102","kev_date_added":null,"published":"2026-07-14"}],"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":["Microsoft"]},"summary":"An attacker can gain privileges via a Trojan horse DLL in the Visual Studio Code installer due to an untrusted search path vulnerability.","url":"https://insights.sbomify.com/CVE-2018-0597/"}