CVE-2023-29011 json
Git for Windows's config file of `connect.exe` is susceptible to malicious placing
published 3y ago modified 5mo ago also EUVD-2023-32624 , GHSA-g4fv-xjqw-q7jm
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository git-for-windows/git. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- git_for_windows_project git_for_windows 2.40.1.1
- gitforwindows git 2.40.1.1
Is CVE-2023-29011 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- git-for-windows git
Classification
- Weakness
-
- CWE-427 Uncontrolled Search Path Element
- Technology feeds
References
-
github.com
/git-for-windows/git/security/advisories/GHSA-g4fv-xjqw-q7jm
vendor-advisory, advisory
-
github.com
/git-for-windows/git/releases/tag/v2.40.1.windows.1
release-notes
Sources
- CVE List CVE-2023-29011
- NVD CVE-2023-29011
- Maintainer advisory GHSA-g4fv-xjqw-q7jm
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of git-for-windows/git published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: git for windows improved version ranges, cpes, etc.