CVE-2022-419538.6HighCWE-426

CVE-2022-41953: Git clone remote code execution vulnerability in git-for-windows

git-for-windows · git

Affected: git-for-windows · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

8.0%probability of exploitation in the next 30 days

94th percentile

050100

Higher than 94% of scored CVEs

8.6HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

git-for-windows · git< 2.39.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Untrusted Search Path · File and Path Handling
Vendor: git-for-windows
Published: January 2023
Band: Possible (1 to 10%), January 2023

CoverageNo articles yet

No CyberSIXT article names CVE-2022-41953 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.