CVE-2019-10776 json
OS command injection in git-diff-apply
published 6y ago modified 4mo ago also GHSA-84cm-v6jp-gjmr , EUVD-2020-0294
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
In "index.js" file line 240, the run command executes the git command with a user controlled variable called remoteUrl. This affects git-diff-apply all versions prior to 0.22.2.
Patch / fix
- npm git-diff-apply 0.22.2
- git-diff-apply_project git-diff-apply 0.22.2
Is CVE-2019-10776 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- snyk.io https://snyk.io/vuln/SNYK-JS-GITDIFFAPPLY-540774 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | git-diff-apply | <0.22.2 |
0.22.2 |
Affected products
- n/a git-diff-apply
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
github.com
/kellyselden/git-diff-apply/commit/106d61d3ae723b4257c2a13e67b95eb40a27e0b5
web, patch, third-party-advisory
-
snyk.io
/vuln/SNYK-JS-GITDIFFAPPLY-540774
web, exploit, patch, third-party-advisory
- snyk.io /vuln/SNYK-JS-GITDIFFAPPLY-540774%2C
-
nvd.nist.gov
/vuln/detail/CVE-2019-10776
advisory
-
snyk.io
/vuln/SNYK-JS-GITDIFFAPPLY-540774,
web
Sources
- CVE List CVE-2019-10776
- GitHub Advisory GHSA-84cm-v6jp-gjmr
- NVD CVE-2019-10776
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.