Approved changes feed: RSS · Atom
cpe:2.3:a:git-for-windows:git:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Git For Windows (05c26518-9257-561a-968f-26868dcd6771) |
|---|---|
| Product | Git (56b1a369-d252-5c74-a35c-8687c372d831) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-32631 |
vulnerable | 2026-06-08 07:57:17.776105 |
Git for Windows: `git clone` from manipulated repositories can leak NTLM hashes to arbitrary servers
HIGH (7.4)
Git for Windows is the Windows port of Git. Versions prior to 2.53.0.windows.3 do not have protections that prevent attackers from obtaining a user's NTLM hash. The NTLM hash can be obtained by tricking users into cloning a malicious repository, or checking out a malicious branch, that accesses an attacker-controlled server. By default, NTLM authentication does not need any user interaction. By brute-forcing the NTLMv2 hash (which is expensive, but possible), credentials can be extracted. This issue has been fixed in version 2.53.0.windows.3.
Published: 2026-04-15T17:26:44.154Z
Updated: 2026-04-15T18:44:04.155Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-66413 |
vulnerable | 2026-06-08 07:41:18.891784 |
Git for Windows leaks NTLM hash when cloning from an attacker-controlled server
HIGH (7.4)
Git for Windows is the Windows port of Git. Prior to 2.53.0(2), it is possible to obtain a user's NTLM hash by tricking them into cloning from a malicious server. Since NTLM hashing is weak, it is possible for the attacker to brute-force the user's account name and password. This vulnerability is fixed in 2.53.0(2).
Published: 2026-03-10T20:34:32.769Z
Updated: 2026-03-11T14:33:36.115Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-29012 |
vulnerable | 2026-06-08 06:02:37.926163 |
Git CMD erroneously executes `doskey.exe` in the current directory, if it exists
HIGH (7.3)
Git for Windows is the Windows port of Git. Prior to version 2.40.1, any user of Git CMD who starts the command in an untrusted directory is impacted by an Uncontrolles Search Path Element vulnerability. Maliciously-placed `doskey.exe` would be executed silently upon running Git CMD. The problem has been patched in Git for Windows v2.40.1. As a workaround, avoid using Git CMD or, if using Git CMD, avoid starting it in an untrusted directory.
Published: 2023-04-25T20:44:05.329Z
Updated: 2025-02-03T18:06:37.041Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-29011 |
vulnerable | 2026-06-08 06:02:37.924689 |
Git for Windows's config file of `connect.exe` is susceptible to malicious placing
HIGH (7.6)
Git for Windows, the Windows port of Git, ships with an executable called `connect.exe`, which implements a SOCKS5 proxy that can be used to connect e.g. to SSH servers via proxies when certain ports are blocked for outgoing connections. The location of `connect.exe`'s config file is hard-coded as `/etc/connectrc` which will typically be interpreted as `C:\etc\connectrc`. Since `C:\etc` can be created by any authenticated user, this makes `connect.exe` susceptible to malicious files being placed there by other users on the same multi-user machine. The problem has been patched in Git for Windows v2.40.1. As a workaround, create the folder `etc` on all drives where Git commands are run, and remove read/write access from those folders. Alternatively, watch out for malicious `<drive>:\etc\connectrc` files on multi-user machines.
Published: 2023-04-25T20:40:30.247Z
Updated: 2025-02-03T18:07:25.939Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-25815 |
vulnerable | 2026-06-08 05:56:10.663167 |
Git looks for localized messages in the wrong place
LOW (3.3)
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:\`.
Published: 2023-04-25T19:51:38.433Z
Updated: 2026-11-02T22:31:41.007Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-23618 |
vulnerable | 2026-06-08 05:56:03.954248 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-22743 |
vulnerable | 2026-06-08 05:54:26.999930 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41953 |
vulnerable | 2026-06-08 05:49:28.961572 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31012 |
vulnerable | 2026-06-08 05:43:39.974353 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24765 |
vulnerable | 2026-06-08 05:41:01.581841 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.