| Name | CVE-2020-11008 |
| Description | Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. This bug is similar to CVE-2020-5260(GHSA-qm7j-c969-7j4q). The fix for that bug still left the door open for an exploit where _some_ credential is leaked (but the attacker cannot control which one). Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that are considered illegal as of the recently published Git versions can cause Git to send a "blank" pattern to helpers, missing hostname and protocol fields. Many helpers will interpret this as matching _any_ URL, and will return some unspecified stored password, leaking the password to an attacker's server. The vulnerability can be triggered by feeding a malicious URL to `git clone`. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The root of the problem is in Git itself, which should not be feeding blank input to helpers. However, the ability to exploit the vulnerability in practice depends on which helpers are in use. Credential helpers which are known to trigger the vulnerability: - Git's "store" helper - Git's "cache" helper - the "osxkeychain" helper that ships in Git's "contrib" directory Credential helpers which are known to be safe even with vulnerable versions of Git: - Git Credential Manager for Windows Any helper not in this list should be assumed to trigger the vulnerability. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | DLA-2182-1, DSA-4659-1 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| git (PTS) | jessie, jessie (lts) | 1:2.1.4-2.1+deb8u14 | fixed |
| stretch (security) | 1:2.11.0-3+deb9u7 | fixed | |
| stretch (lts), stretch | 1:2.11.0-3+deb9u11 | fixed | |
| buster (security), buster, buster (lts) | 1:2.20.1-2+deb10u9 | fixed | |
| bullseye | 1:2.30.2-1+deb11u2 | fixed | |
| bullseye (security) | 1:2.30.2-1+deb11u3 | fixed | |
| bookworm (security), bookworm | 1:2.39.5-0+deb12u1 | fixed | |
| trixie | 1:2.45.2-1 | fixed | |
| sid | 1:2.45.2-1.2 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| git | source | wheezy | (not affected) | |||
| git | source | jessie | 1:2.1.4-2.1+deb8u10 | DLA-2182-1 | ||
| git | source | stretch | 1:2.11.0-3+deb9u7 | DSA-4659-1 | ||
| git | source | buster | 1:2.20.1-2+deb10u3 | DSA-4659-1 | ||
| git | source | (unstable) | 1:2.26.2-1 |
https://lore.kernel.org/lkml/xmqq4kterq5s.fsf@gitster.c.googlers.com/
https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=a88dbd2f8c7fd8c1e2f63483da03bd6928e8791f
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=73aafe9bc27585554181c58871a25e6d0f58a3dc
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=24036686c4af84c9e84e486ef3debab6e6d8e6b5
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=8ba8ed568e2a3b75ee84c49ddffb026fde1a0a91
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=a2b26ffb1a81aa23dd14453f4db05d8fe24ee7cc
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=fe29a9b7b0236d3d45c254965580d6aff7fa8504
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=c44088ecc4b0722636e0a305f9608d3047197282
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=e7fab62b736cca3416660636e46f0be8386a5030
Fixed by: https://git.kernel.org/pub/scm/git/git.git/commit/?id=1a3609e402a062ef7b11f197fe96c28cabca132c
[wheezy] - git <not-affected> (Vulnerable code not present)
While the fix for CVE-2020-5260 in 2.x versions of Git left the door open
for this additional vulnerability, the CVE-2020-5260 fix applied in the
1.7 version of Git in wheezy was more coarse (newline in a credential host
specification always fails). As a result, the POC for this CVE fails,
indicating that the wheezy version of Git is not vulnerable.