{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16765 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16765 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16765 is a high-severity code injection vulnerability in github vscode-codeql, published on 25 Nov 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-16765 and fix it if it is affected.\n\nWhat it is: CVE-2019-16765 is a high-severity code injection vulnerability in github vscode-codeql, published on 25 Nov 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-16765 in the wild and no public exploit code.\n\nAffected product: github vscode-codeql. 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-16765/ (Markdown: https://insights.sbomify.com/CVE-2019-16765/index.md)","id":"CVE-2019-16765","markdown":"https://insights.sbomify.com/CVE-2019-16765/index.md","name":"CVE-2019-16765","record":{"aliases":["GHSA-wf4x-8mpj-r42q","GHSA-x3w4-7cmr-9gv2"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VS Code extension","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening a malicious workspace with the CodeQL extension active.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"codeql","vendor":"microsoft"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-250","name":"Execution with Unnecessary Privileges"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"If an attacker can get a user to open a specially prepared directory tree as a workspace in Visual Studio Code with the CodeQL extension active, arbitrary code of the attacker's choosing may be executed on the user's behalf. This is fixed in version 1.0.1 of the extension. Users should upgrade to this version using Visual Studio Code Marketplace's upgrade mechanism. After upgrading, the codeQL.cli.executablePath setting can only be set in the per-user settings, and not in the per-workspace settings. More information about VS Code settings can be found here.","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":"Code injection in vscode-codeql","id":"CVE-2019-16765","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"2FA bypass in Wagtail through new device path","id":"CVE-2019-16766"},"packages":[],"prev":{"headline":"PowAssent is susceptible to denial of service attacks","id":"CVE-2019-16764"},"products":["vscode-codeql"],"published":"2019-11-25","related":[],"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":["github"]},"summary":"Attackers can execute arbitrary code by tricking users into opening a malicious workspace with the CodeQL extension active.","url":"https://insights.sbomify.com/CVE-2019-16765/"}