{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26233 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26233 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26233 is a high-severity command injection vulnerability in microsoft Git-Credential-Manager-Core, published on 8 Dec 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-26233 and fix it if it is affected.\n\nWhat it is: CVE-2020-26233 is a high-severity command injection vulnerability in microsoft Git-Credential-Manager-Core, published on 8 Dec 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-26233 in the wild and no public exploit code.\n\nAffected product: microsoft Git-Credential-Manager-Core. 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-26233/ (Markdown: https://insights.sbomify.com/CVE-2020-26233/index.md)","id":"CVE-2020-26233","markdown":"https://insights.sbomify.com/CVE-2020-26233/index.md","name":"CVE-2020-26233","record":{"aliases":["GHSA-2gq7-ww4j-3m76"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Git Credential Manager","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code on Windows by placing a malicious git.exe in a repository cloned with submodules, affecting Git Credential Manager Core users.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"git_credential_manager_core","vendor":"microsoft"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"description":"Git Credential Manager Core (GCM Core) is a secure Git credential helper built on .NET Core that runs on Windows and macOS. In Git Credential Manager Core before version 2.0.289, when recursively cloning a Git repository on Windows with submodules, Git will first clone the top-level repository and then recursively clone all submodules by starting new Git processes from the top-level working directory. If a malicious git.exe executable is present in the top-level repository then this binary will be started by Git Credential Manager Core when attempting to read configuration, and not git.exe as found on the %PATH%. This only affects GCM Core on Windows, not macOS or Linux-based distributions. GCM Core version 2.0.289 contains the fix for this vulnerability, and is available from the project's GitHub releases page. GCM Core 2.0.289 is also bundled in the latest Git for Windows release; version 2.29.2(3). As a workaround, users should avoid recursively cloning untrusted repositories with the --recurse-submodules option.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-05-24","github_poc":2,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-05-24T08:49:01Z","kind":"github_poc","ref":"https://github.com/whr819987540/test_CVE-2020-26233","stars":0,"title":null},{"date":"2022-10-28T05:56:45Z","kind":"github_poc","ref":"https://github.com/an1p3lg5/CVE-2020-26233","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"Remote Code Execution in Git Credential Manager Core","id":"CVE-2020-26233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":0,"n_references":5,"next":{"headline":"Disabled Hostname Verification in OpenCast","id":"CVE-2020-26234"},"packages":[],"prev":{"headline":"Open redirect in Jupyter Server","id":"CVE-2020-26232"},"products":["Git-Credential-Manager-Core"],"published":"2020-12-08","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["microsoft"]},"summary":"Attackers can execute arbitrary code on Windows by placing a malicious git.exe in a repository cloned with submodules, affecting Git Credential Manager Core users.","url":"https://insights.sbomify.com/CVE-2020-26233/"}