{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-1211 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-1211 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-1211 is a high-severity vulnerability in Microsoft Visual Studio 2017, published on 14 Aug 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-2019-1211 and fix it if it is affected.\n\nWhat it is: CVE-2019-1211 is a high-severity vulnerability in Microsoft Visual Studio 2017, published on 14 Aug 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-2019-1211 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-2019-1211/ (Markdown: https://insights.sbomify.com/CVE-2019-1211/index.md)","id":"CVE-2019-1211","markdown":"https://insights.sbomify.com/CVE-2019-1211/index.md","name":"CVE-2019-1211","record":{"aliases":["GHSA-78g9-438v-4f34"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Git for Visual Studio","requires_auth":"low_privilege","summary":"An attacker can execute code as another local user by modifying Git configuration files before installation, requiring victim interaction.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio_2017","vendor":"microsoft"},{"product":"visual_studio_2019","vendor":"microsoft"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"An elevation of privilege vulnerability exists in Git for Visual Studio when it improperly parses configuration files. An attacker who successfully exploited the vulnerability could execute code in the context of another local user.\nTo exploit the vulnerability, an authenticated attacker would need to modify Git configuration files on a system prior to a full installation of the application. The attacker would then need to convince another user on the system to execute specific Git commands.\nThe update addresses the issue by changing the permissions required to edit configuration files.","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":"Git for Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2019-1211","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":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Windows DHCP Server Denial of Service Vulnerability","id":"CVE-2019-1212"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-1210"},"products":["Microsoft Visual Studio 2017","Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)","Microsoft Visual Studio 2019 version 16.0","Microsoft Visual Studio 2019 version 16.2"],"published":"2019-08-14","related":[{"cvss_score":8.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2025-21178","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1349","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1350","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1352","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Visual Studio 2017","id":"CVE-2019-1354","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":7.8,"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2023-28296","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.8,"headline":"Visual Studio Elevation of Privilege Vulnerability","id":"CVE-2023-21566","kev_date_added":null,"published":"2023-02-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Microsoft"]},"summary":"An attacker can execute code as another local user by modifying Git configuration files before installation, requiring victim interaction.","url":"https://insights.sbomify.com/CVE-2019-1211/"}