{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-0900 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-0900 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-0900 is a medium-severity vulnerability in Microsoft Visual Studio 2017, published on 15 Apr 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-0900 and fix it if it is affected.\n\nWhat it is: CVE-2020-0900 is a medium-severity vulnerability in Microsoft Visual Studio 2017, published on 15 Apr 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-0900 in the wild and no public exploit code.\n\nAffected product: Microsoft Visual Studio 2017. 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-0900/ (Markdown: https://insights.sbomify.com/CVE-2020-0900/index.md)","id":"CVE-2020-0900","markdown":"https://insights.sbomify.com/CVE-2020-0900/index.md","name":"CVE-2020-0900","record":{"aliases":["GHSA-m8rj-v5pg-g6vq"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Visual Studio IDE","requires_auth":"low_privilege","summary":"Attackers can gain elevated privileges by exploiting improper file handling in the Visual Studio Extension Installer Service.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio_2015","vendor":"microsoft"},{"product":"visual_studio_2017","vendor":"microsoft"},{"product":"visual_studio_2019","vendor":"microsoft"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"An elevation of privilege vulnerability exists when the Visual Studio Extension Installer Service improperly handles file operations, aka 'Visual Studio Extension Installer Service Elevation of Privilege Vulnerability'.","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 Microsoft Visual Studio","id":"CVE-2020-0900","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio_2017","products":["microsoft:visual_studio_2017","microsoft:visual_studio_2019"],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Microsoft Excel Remote Code Execution Vulnerability","id":"CVE-2020-0901"},"packages":[],"prev":{"headline":"Privilege escalation in Microsoft Visual Studio 2017 version 15.9 (includes 15.1 - 15.8)","id":"CVE-2020-0899"},"products":["Microsoft Visual Studio","Microsoft Visual Studio 2017 version 15.9 (includes 15.1 - 15.8)","Microsoft Visual Studio 2019","Microsoft Visual Studio 2019 version 16.4 (includes 16.0 - 16.3)","Microsoft Visual Studio 2019 version 16.5"],"published":"2020-04-15","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Microsoft Visual Studio","id":"CVE-2020-0793","kev_date_added":null,"published":"2020-03-12"},{"cvss_score":7.8,"headline":"Privilege escalation in Microsoft Visual Studio","id":"CVE-2020-0810","kev_date_added":null,"published":"2020-03-12"},{"cvss_score":7.8,"headline":"Privilege escalation in Microsoft Visual Studio","id":"CVE-2018-0952","kev_date_added":null,"published":"2018-08-15"}],"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-08-04","vendors":["Microsoft"]},"summary":"Attackers can gain elevated privileges by exploiting improper file handling in the Visual Studio Extension Installer Service.","url":"https://insights.sbomify.com/CVE-2020-0900/"}