CVE-2020-11008
No exploitation reported by the sources we read.
- Published2020-04-21
- Fixed in2.26.2 · 2.25.4 · 2.24.3 · 2.23.3 · 2.22.4 · 2.21.3
- WeaknessCWE-20 · CWE-522
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2020-04-2119:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-11008?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-11008?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.26 | ≥ 2.26.0, < 2.26.2 | 2.26.2 | NVD |
| 2.25 | ≥ 2.25.0, < 2.25.4 | 2.25.4 | NVD |
| 2.24 | ≥ 2.24.0, < 2.24.3 | 2.24.3 | NVD |
| 2.23 | ≥ 2.23.0, < 2.23.3 | 2.23.3 | NVD |
| 2.22 | ≥ 2.22.0, < 2.22.4 | 2.22.4 | NVD |
| 2.21 | ≥ 2.21.0, < 2.21.3 | 2.21.3 | NVD |
| 2.20 | ≥ 2.20.0, < 2.20.4 | 2.20.4 | NVD |
| 2.19 | ≥ 2.19.0, < 2.19.5 | 2.19.5 | NVD |
| 2.18 | ≥ 2.18.0, < 2.18.4 | 2.18.4 | NVD |
| 2.17 | < 2.17.5 | 2.17.5 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.4 | = 16.04 | no fix published | NVD |
| 18.4 | = 18.04 | no fix published | NVD |
| 19.10 | = 19.10 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 31.x | = 31 | no fix published | NVD |
| 32.x | = 32 | no fix published | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Git-scm git to 2.26.2 · 2.25.4 · 2.24.3 · 2.23.3 · 2.22.4 · 2.21.3 · 2.20.4 · 2.19.5
Advisories and patches
- github.comPatch
- github.comPatch
- github.comMitigation · Patch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2020-04-21
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-11008?
Is CVE-2020-11008 actively exploited?
What is the CVSS score for CVE-2020-11008?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.