Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2020-11008: Malicious URLs can still cause Git to send a stored credential to the wrong server

HighCVSS 7.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.8% (FIRST EPSS); higher than 90.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: git (Alpine:v3.10) 2.22.4-r0; git (Alpine:v3.11) 2.24.3-r0; git (Alpine:v3.12) 2.26.2-r0.
  • Severity is disputed: the assigning authority (CNA) scores it 4.0, NVD 7.5.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to git (Alpine:v3.10) 2.22.4-r0; git (Alpine:v3.11) 2.24.3-r0; git (Alpine:v3.12) 2.26.2-r0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Apr 21, 2020
Updated
Jun 16, 2026
EPSS
3.8% · 90th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.8%

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
4.0
3.5 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-11008

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
git-scmgit
canonicalubuntu linux
debiandebian linux
fedoraprojectfedora

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • git git

    • < 2.17.5, >= 2.18.0, < 2.18.4, >= 2.19.0, 2.19.5, >= 2.20.0, < 2.20.4, >= 2.21.0, < 2.21.3, >= 2.22.0, < 2.22.4, >= 2.23.0, < 2.23.3, >= 2.24.0, < 2.24.3, >= 2.25.0, < 2.25.4, >= 2.26.0, < 2.26.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10gitfrom 2.18.0 · before 2.22.4-r02.22.4-r0
Alpine:v3.11gitfrom 2.18.0 · before 2.24.3-r02.24.3-r0
Alpine:v3.12gitfrom 2.18.0 · before 2.26.2-r02.26.2-r0
Alpine:v3.8gitfrom 2.18.0 · before 2.18.4-r02.18.4-r0
Alpine:v3.9gitfrom 2.18.0 · before 2.20.4-r02.20.4-r0
Debian:10gitbefore 1:2.20.1-2+deb10u31:2.20.1-2+deb10u3
Debian:12gitbefore 1:2.26.2-11:2.26.2-1
Debian:8gitbefore 1:2.1.4-2.1+deb8u101:2.1.4-2.1+deb8u10
Debian:9gitbefore 1:2.11.0-3+deb9u71:2.11.0-3+deb9u7
openSUSE:Leap 15.1gitbefore 2.26.1-lp151.4.9.12.26.1-lp151.4.9.1
openSUSE:Tumbleweedgitbefore 2.33.0-1.32.33.0-1.3
Red Hat:enterprise_linux:7::clientemacs-gitbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientemacs-git-elbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgitbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-allbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-bzrbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-cvsbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-daemonbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-debuginfobefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-emailbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-gnome-keyringbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-guibefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-hgbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8
Red Hat:enterprise_linux:7::clientgit-instawebbefore 0:1.8.3.1-23.el7_80:1.8.3.1-23.el7_8

+96

Other highest-scoring records for the same primary product.

  • CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows…
    68This week
  • CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV
    63This week
  • CVE-2021-21300malicious repositories can execute remote code while cloning
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2019-1348Jan 24, 2020 · An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6.
    13Monitor
  • ← EarlierCVE-2019-1353Jan 24, 2020 · An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6.
    40Plan
  • Later →CVE-2021-40330Aug 31, 2021 · git_connect_git in connect.c in Git before 2.30.1 allows a repository path to contain a newline character, which may result in unexpected…
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:git2.22.4-r0 · Alpine:v3.10Package registry (OSV)
debian:git1:2.26.2-1 · Debian:12Package registry (OSV)
opensuse:git2.26.1-lp151.4.9.1 · openSUSE:Leap 15.1Package registry (OSV)
red hat:rh-git218-git0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-all0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-core0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-core-doc0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-cvs0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-daemon0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-debuginfo0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-email0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-gui0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-instaweb0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-p40:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-git218-git-subtree0:2.18.4-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
suse:git2.26.1-3.25.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

References

All records