Skip to content
Fencer Intel
high 7.8

CVE-2019-19604 json

Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before 2.23.1, and 2.24.x…

published 6y ago modified 4mo ago also EUVD-2019-9219

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.7%
EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before 2.23.1, and 2.24.x before 2.24.1 because a "git submodule update" operation can run commands found in the .gitmodules file of a malicious repository.

Patch / fix

  • git-scm git 2.20.0, 2.21.1, 2.22.2, 2.23.1, 2.24.1
  • git Debian 14, Debian 13, Debian 12 1:2.24.0-2

debian advisories DEBIAN-CVE-2019-19604

  • git SLE Module for Development Tools 15 SP1, SLE Module for Basesystem 15 SP1 2.26.1-3.25.2
  • git SLE Module for Development Tools 15 SP1, SLE Module for Development Tools 15, SLE Module for Basesystem 15 SP1 +1 more 2.16.4-3.17.2
  • perl-Authen-SASL SLE Module for Development Tools 15 SP1, SLE Module for Development Tools 15 2.16-1.3.1
  • perl-Net-SMTP-SSL SLE Module for Development Tools 15 SP1, SLE Module for Development Tools 15 1.04-1.3.1
  • git SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES for SAP 12 SP3 +14 more 2.12.3-27.22.1

suse advisories SUSE-SU-2020:1121-1SUSE-SU-2020:0045-1SUSE-SU-2019:3311-1

  • git openSUSE Tumbleweed 2.33.0-1.3
  • git openSUSE Leap 15.1 2.26.1-lp151.4.9.1
  • git openSUSE Leap 15.1 2.16.4-lp151.4.3.1
  • perl-Authen-SASL openSUSE Leap 15.1 2.16-lp151.3.3.1
  • perl-Net-SMTP-SSL openSUSE Leap 15.1 1.04-lp151.3.3.1

opensuse advisories openSUSE-SU-2024:10786-1openSUSE-SU-2020:0598-1openSUSE-SU-2020:0123-1

  • git Alpine 3.10 2.22.2-r0
  • git Alpine 3.24, Alpine 3.23, Alpine 3.22 +11 more 2.24.1-r0

alpine advisories ALPINE-CVE-2019-19604

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • git Arch Linux 2.24.1-1

arch linux advisories AVG-1073

Is CVE-2019-19604 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 Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-19604 updated cvss 7.8

git: Recursive clone followed by a submodule update could execute code contained within repository without the user explicitly consent

  • Red Hat Enterprise Linux 6 git, gitk, gitweb, git-all, git-cvs, git-gui, +6 more Red Hat Enterprise Linux 7 git, gitk, git-hg, git-p4, gitweb, git-all, +12 more Red Hat Enterprise Linux 8 git, gitk, gitweb, git-all, git-gui, git-svn, +8 more Red Hat Fuse 7 camel-git camel-git Red Hat JBoss Fuse 6 camel-git camel-git Red Hat OpenShift Container Platform 3.11 jenkins-2-plugins
    +2 more products
    Red Hat OpenShift Container Platform 4 jenkins-2-plugins Red Hat Software Collections rh-git218-git, rh-git218-gitk, rh-git218-git-p4, rh-git218-gitweb, rh-git218-git-all, rh-git218-git-cvs, +9 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.71% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • gitlab.com https://gitlab.com/gitlab-com/gl-security/disclosures/blob/master/003_git_submodule/advisory.md referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command
  • CWE-862 Missing Authorization

References

Sources

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.