CVE-2020-11008mediumCWE-20

CVE-2020-11008: medium-severity vulnerability in git

Malicious URLs can still cause Git to send a stored credential to the wrong server

Published · Updated

Follow this CVE+ Monitor git+ Monitor git

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 4epss 3.9%
In short

Git can be tricked into sending stored credentials (like passwords) to an attacker's server when processing specially-crafted malicious URLs. This happens because Git may send incomplete information to credential helpers, which then return any matching stored password instead of rejecting the request.

Technical detail

Git's credential helper interface can receive malformed URL patterns (missing hostname and protocol fields) from specially-crafted URLs, causing helpers to match against any stored credential and leak sensitive passwords. The vulnerability is triggered via git clone or automated systems like Git submodules; exploitation depends on which credential helpers are configured (Git's store, cache, and osxkeychain helpers are known to be vulnerable). Impact includes unauthorized disclosure of stored credentials to attacker-controlled servers.

Summary generated and translated by AI from the official 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
Affected products
git · git
Related CVEs — git

In the same product, most dangerous first.

CVE-2025-48384HIGHGit allows arbitrary code execution through broken config quotingEPSS 4.5%KEVCVE-2021-21300HIGHmalicious repositories can execute remote code while cloningEPSS 88.5%CVE-2022-23521CRITICALgitattributes parsing integer overflow in gitEPSS 56.3%CVE-2023-25652HIGH"git apply --reject" partially-controlled arbitrary file writeEPSS 51.9%CVE-2022-41903CRITICALInteger overflow in `git archive`, `git log --format` leading to RCE in gitEPSS 44.3%CVE-2024-32002CRITICALGit's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code ExecutionEPSS 29.2%