Git up to 2.40.0 on Windows git.exe path traversal

Summaryinfo

A vulnerability was found in Git on Windows. It has been declared as critical. This vulnerability affects unknown code of the file git.exe. Such manipulation leads to path traversal. This vulnerability is referenced as CVE-2023-25815. The attack can only be performed from a local environment. Furthermore, an exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Git on Windows (Versioning Software). Affected by this issue is some unknown processing of the file git.exe. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is integrity, and availability. CVE summarizes:

In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the `gettext()` function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path `C:\mingw64\share\locale` to look for localized messages. And since any authenticated user has the permission to create folders in `C:\` (and since `C:\mingw64` does not typically exist), it is possible for low-privilege users to place fake messages in that location where `git.exe` will pick them up in version 2.40.1. This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a `C:\mingw64` folder and leave it empty. Users who have administrative rights may remove the permission to create folders in `C:\`.

The weakness was published 04/25/2023 as GHSA-9w66-8mq8-5vm8. The advisory is available at github.com. This vulnerability is handled as CVE-2023-25815 since 02/15/2023. Technical details as well as a public exploit are known. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.

The exploit is available at axcheron.github.io. It is declared as proof-of-concept.

Upgrading to version 2.40.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Versioning Software

Name

• Git

Version

• 0.0.20080710
• 0.0.20090320
• 0.1.1
• 0.7.2
• 0.10.3
• 0.22.2
• 1
• 1.0.0
• 1.0.0b
• 1.0.1
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.1.0
• 1.1.0.0
• 1.1.1
• 1.1.2
• 1.1.3
• 1.1.4
• 1.1.5
• 1.3.0
• 1.3.1
• 1.4.2.2
• 1.5.2.1
• 1.5.5.3
• 1.5.5.4
• 1.5.6.1
• 1.5.6.2
• 1.5.6.3
• 1.6.0.2
• 1.7.0
• 1.8.1.3
• 1.8.2
• 1.9.3
• 1.11.0
• 1.13.0
• 1.13.2
• 2.0
• 2.0.2
• 2.0.289
• 2.1.1
• 2.1.2
• 2.3.10
• 2.4.9
• 2.4.10
• 2.4.12
• 2.5.0
• 2.5.3
• 2.5.4
• 2.5.5
• 2.5.6
• 2.6.0
• 2.6.1
• 2.6.6
• 2.6.7
• 2.7.4
• 2.7.5
• 2.8.0
• 2.8.0-rc3
• 2.8.4
• 2.8.5
• 2.9.3
• 2.9.4
• 2.10.2
• 2.10.3
• 2.10.5
• 2.11.1
• 2.11.2
• 2.11.3
• 2.11.4
• 2.12.0
• 2.12.2
• 2.12.3
• 2.12.4
• 2.12.5
• 2.13.2
• 2.13.5
• 2.13.6
• 2.13.7
• 2.14.1
• 2.14.2
• 2.14.3
• 2.14.4
• 2.14.5
• 2.14.6
• 2.15.1
• 2.15.2
• 2.15.3
• 2.15.4
• 2.16.3
• 2.16.4
• 2.16.5
• 2.16.6
• 2.17.0
• 2.17.1
• 2.17.2
• 2.17.3
• 2.17.4
• 2.18.0
• 2.18.1
• 2.18.2
• 2.18.3
• 2.19.0
• 2.19.1
• 2.19.2
• 2.19.3
• 2.19.4
• 2.20.1
• 2.20.2
• 2.20.3
• 2.21.0
• 2.21.1
• 2.21.2
• 2.22.1
• 2.22.2
• 2.22.3
• 2.23.0
• 2.23.1
• 2.23.2
• 2.24.0
• 2.24.1
• 2.24.2
• 2.25.2
• 2.25.3
• 2.26.0
• 2.26.1
• 2.30.1
• 2.30.5
• 2.30.6
• 2.30.8
• 2.30.9
• 2.31.1-2
• 2.31.3
• 2.31.4
• 2.31.5
• 2.31.6
• 2.31.7
• 2.31.8
• 2.32.2
• 2.32.3
• 2.32.4
• 2.32.5
• 2.32.6
• 2.32.7
• 2.33.3
• 2.33.4
• 2.33.5
• 2.33.6
• 2.33.7
• 2.33.8
• 2.34.3
• 2.34.4
• 2.34.5
• 2.34.6
• 2.34.7
• 2.34.8
• 2.35.3
• 2.35.4
• 2.35.5
• 2.35.6
• 2.35.7
• 2.35.8
• 2.36.1
• 2.36.2
• 2.36.3
• 2.36.4
• 2.36.5
• 2.36.6
• 2.37.0
• 2.37.1
• 2.37.3
• 2.37.4
• 2.37.5
• 2.37.6
• 2.37.7
• 2.38.3
• 2.38.4
• 2.38.5
• 2.39.1
• 2.39.2
• 2.39.3
• 2.40.0

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion