{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1414 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-1414 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-1414 is a high-severity vulnerability in Microsoft Visual Studio Code, published on 24 Jan 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-2019-1414 and fix it if it is affected.\n\nWhat it is: CVE-2019-1414 is a high-severity vulnerability in Microsoft Visual Studio Code, published on 24 Jan 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-2019-1414 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-2019-1414/ (Markdown: https://insights.sbomify.com/CVE-2019-1414/index.md)","id":"CVE-2019-1414","markdown":"https://insights.sbomify.com/CVE-2019-1414/index.md","name":"CVE-2019-1414","record":{"aliases":["GHSA-p323-w8wx-j9rr"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Visual Studio Code","requires_auth":"low_privilege","summary":"An attacker with local access can escalate privileges by exploiting an exposed debug listener in Visual Studio Code.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"visual_studio_code","vendor":"microsoft"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An elevation of privilege vulnerability exists in Visual Studio Code when it exposes a debug listener to users of a local computer, aka 'Visual Studio Code 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":false,"headline":"Privilege escalation in Visual Studio Code","id":"CVE-2019-1414","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:visual_studio_code","products":["microsoft:visual_studio_code"],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Windows","id":"CVE-2019-1415"},"packages":[],"prev":{"headline":"Security feature bypass in Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1607 for 32-bit Systems","id":"CVE-2019-1413"},"products":["Visual Studio Code"],"published":"2020-01-24","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":"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 with local access can escalate privileges by exploiting an exposed debug listener in Visual Studio Code.","url":"https://insights.sbomify.com/CVE-2019-1414/"}