{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-22743 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-22743 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22743 is a high-severity code injection vulnerability in git-for-windows git, published on 14 Feb 2023. 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-2023-22743 and fix it if it is affected.\n\nWhat it is: CVE-2023-22743 is a high-severity code injection vulnerability in git-for-windows git, published on 14 Feb 2023. 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-2023-22743 in the wild and no public exploit code.\n\nAffected product: git-for-windows git. 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-2023-22743/ (Markdown: https://insights.sbomify.com/CVE-2023-22743/index.md)","id":"CVE-2023-22743","markdown":"https://insights.sbomify.com/CVE-2023-22743/index.md","name":"CVE-2023-22743","record":{"aliases":[],"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 Windows","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code with elevated privileges by placing malicious DLLs in specific directories during Git for Windows installation.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"git_for_windows","vendor":"git_for_windows_project"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"Git for Windows is the Windows port of the revision control system Git. Prior to Git for Windows version 2.39.2, by carefully crafting DLL and putting into a subdirectory of a specific name living next to the Git for Windows installer, Windows can be tricked into side-loading said DLL. This potentially allows users with local write access to place malicious payloads in a location where automated upgrades might run the Git for Windows installer with elevation. Version 2.39.2 contains a patch for this issue. Some workarounds are available. Never leave untrusted files in the Downloads folder or its sub-folders before executing the Git for Windows installer, or move the installer into a different directory before executing it.","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":"Git for Windows' installer is susceptible to DLL side loading attacks","id":"CVE-2023-22743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"Buffer Overlow in TSS2_RC_Decode in tpm2-tss","id":"CVE-2023-22745"},"packages":[],"prev":{"headline":"libgit2 fails to verify SSH keys by default","id":"CVE-2023-22742"},"products":["git"],"published":"2023-02-14","related":[{"cvss_score":8.6,"headline":"gitk can inadvertently call executables in the worktree","id":"CVE-2023-23618","kev_date_added":null,"published":"2023-02-14"},{"cvss_score":7.8,"headline":"Other in Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)","id":"CVE-2022-24767","kev_date_added":null,"published":"2022-04-12"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2016-9274","kev_date_added":null,"published":"2016-11-11"},{"cvss_score":7.6,"headline":"Git for Windows's config file of `connect.exe` is susceptible to malicious placing","id":"CVE-2023-29011","kev_date_added":null,"published":"2023-04-25"},{"cvss_score":7.3,"headline":"Git CMD erroneously executes `doskey.exe` in the current directory, if it exists","id":"CVE-2023-29012","kev_date_added":null,"published":"2023-04-25"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["git-for-windows"]},"summary":"Attackers can execute arbitrary code with elevated privileges by placing malicious DLLs in specific directories during Git for Windows installation.","url":"https://insights.sbomify.com/CVE-2023-22743/"}