Vulnerability record · CVE-2022-41953 · published 17 January 2023
CVE-2022-41953: Git-scm git untrusted search path vulnerability
Git Scm · Git
Git GUI is a convenient graphical tool that comes with Git for Windows. Its target audience is users who are uncomfortable with using Git on the command-line. Git GUI has a function to clone repositories. Immediately after the local clone is available, Git GUI will automatically post-process it, among other things running a spell checker called `aspell.exe` if it was found. Git GUI is implemented as a Tcl/Tk script. Due to the unfortunate design of Tcl on Windows, the search path when looking for an executable _always includes the current directory_. Therefore, malicious repositories can ship with an `aspell.exe` in their top-level directory which is executed by Git GUI without giving the user a chance to inspect it first, i.e. running untrusted code. This issue has been addressed in version 2.39.1. Users are advised to upgrade. Users unable to upgrade should avoid using Git GUI for cloning. If that is not a viable option, at least avoid cloning from untrusted sources.
Description
Git GUI is a convenient graphical tool that comes with Git for Windows. Its target audience is users who are uncomfortable with using Git on the command-line. Git GUI has a function to clone repositories. Immediately after the local clone is available, Git GUI will automatically post-process it, among other things running a spell checker called `aspell.exe` if it was found. Git GUI is implemented as a Tcl/Tk script. Due to the unfortunate design of Tcl on Windows, the search path when looking for an executable _always includes the current directory_. Therefore, malicious repositories can ship with an `aspell.exe` in their top-level directory which is executed by Git GUI without giving the user a chance to inspect it first, i.e. running untrusted code. This issue has been addressed in version 2.39.1. Users are advised to upgrade. Users unable to upgrade should avoid using Git GUI for cloning. If that is not a viable option, at least avoid cloning from untrusted sources.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://github.com/git-for-windows/git/commit/7360767e8dfc1895a932324079f7d45d7791d39f | PatchThird Party Advisory |
| https://github.com/git-for-windows/git/pull/4219 | PatchThird Party Advisory |
| https://github.com/git-for-windows/git/security/advisories/GHSA-v4px-mx59-w99c | PatchThird Party Advisory |
| https://www.tcl.tk/man/tcl8.6/TclCmd/exec.html#M23 | Third Party Advisory |
| https://github.com/git-for-windows/git/commit/7360767e8dfc1895a932324079f7d45d7791d39f | PatchThird Party Advisory |
| https://github.com/git-for-windows/git/pull/4219 | PatchThird Party Advisory |
| https://github.com/git-for-windows/git/security/advisories/GHSA-v4px-mx59-w99c | PatchThird Party Advisory |
| https://www.tcl.tk/man/tcl8.6/TclCmd/exec.html#M23 | Third Party Advisory |
Track CVE-2022-41953 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2022-41953), CISA KEV, FIRST EPSS (scores of 2026-09-28). This page is refreshed as NVD updates the record.