8.6
CWE
426
Advisory Published
Updated

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

First published: Tue Jan 17 2023(Updated: )

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.

Credit: security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Git-scm Git<2.39.1
Microsoft Windows

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is CVE-2022-41953?

    CVE-2022-41953 is a vulnerability in Git GUI, a graphical tool that comes with Git for Windows, that allows an attacker to execute arbitrary code.

  • What is the severity of CVE-2022-41953?

    CVE-2022-41953 has a severity rating of 7.8 (high).

  • How does CVE-2022-41953 impact Git GUI?

    CVE-2022-41953 allows an attacker to execute arbitrary code through Git GUI's function to clone repositories.

  • What is the affected software of CVE-2022-41953?

    The affected software of CVE-2022-41953 is Git-scm Git versions up to and excluding 2.39.1.

  • How can I fix CVE-2022-41953?

    To fix CVE-2022-41953, it is recommended to update Git-scm Git to a version beyond 2.39.1.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203