CVE-2022-24437

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 10.4%, top 7% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 4%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The package git-pull-or-clone before 2.0.2 are vulnerable to Command Injection due to the use of the --upload-pack feature of git which is also supported for git clone. The source includes the use of the secure child process API spawn(). However, the outpath parameter passed to it may be a command-line argument to the git clone command and result in arbitrary command injection.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
88.9%
KEV
Not listed

Published

May 1, 2022

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 6, 2026
⚠️ Active exploitation confirmed. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic🔴 Active Exploitation

Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') in git-pull-or-clone | CVE-2022-24437 | Snyk

https://snyk.io/vuln/SNYK-JS-GITPULLORCLONE-2434307
github_commit

commit f9ce092be13c (feross/git-pull-or-clone)

Fix landed in feross/git-pull-or-clone commit f9ce092be13c — awaiting tagged release

https://github.com/feross/git-pull-or-clone/commit/f9ce092be13cc32e685dfa26e7705e9c6e3108a3
generic

Command Injection vulnerability in [email protected] · GitHub

https://gist.github.com/lirantal/327e9dd32686991b5a1fa6341aac2e7b

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
git-pull-or-clone—2.0.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-09 19:07 UTCEPSS rescore
  3. 2026-07-08 15:12 UTCEPSS rescore
  4. 2026-07-07 13:44 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-06 02:21 UTCEPSS rescore
  8. 2026-07-05 02:28 UTCEPSS rescore
  9. 2026-07-04 06:29 UTCEPSS rescore
  10. 2026-07-04 06:29 UTCEPSS rescore
  11. 2026-07-01 15:04 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-29 12:02 UTCOSV refresh
  15. 2026-06-28 14:06 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-27 03:07 UTCEPSS rescore
  19. 2026-06-25 13:48 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-22 14:24 UTCEPSS rescore
  25. 2026-06-21 14:55 UTCEPSS rescore
Show 46 more
  1. 2026-06-21 14:55 UTCEPSS rescore
  2. 2026-06-21 01:58 UTCEPSS rescore
  3. 2026-06-21 01:58 UTCEPSS rescore
  4. 2026-06-18 17:51 UTCEPSS rescore
  5. 2026-06-18 17:51 UTCEPSS rescore
  6. 2026-06-17 17:51 UTCEPSS rescore
  7. 2026-06-17 17:51 UTCEPSS rescore
  8. 2026-06-16 17:51 UTCEPSS rescore
  9. 2026-06-15 17:46 UTCEPSS rescore
  10. 2026-06-14 23:15 UTCEPSS rescore
  11. 2026-06-14 23:15 UTCEPSS rescore
  12. 2026-06-13 22:58 UTCEPSS rescore
  13. 2026-06-13 22:58 UTCEPSS rescore
  14. 2026-06-12 23:10 UTCEPSS rescore
  15. 2026-06-12 23:10 UTCEPSS rescore
  16. 2026-06-12 03:27 UTCOSV refresh
  17. 2026-06-11 13:58 UTCEPSS rescore
  18. 2026-06-11 13:58 UTCEPSS rescore
  19. 2026-06-10 22:16 UTCEPSS rescore
  20. 2026-06-10 13:20 UTCEPSS rescore
  21. 2026-06-07 15:23 UTCEPSS rescore
  22. 2026-06-07 15:23 UTCEPSS rescore
  23. 2026-06-06 13:46 UTCEPSS rescore
  24. 2026-06-06 13:46 UTCEPSS rescore
  25. 2026-06-05 22:45 UTCEPSS rescore
  26. 2026-06-05 06:09 UTCEPSS rescore
  27. 2026-06-05 06:09 UTCEPSS rescore
  28. 2026-06-04 13:11 UTCEPSS rescore
  29. 2026-06-04 13:11 UTCEPSS rescore
  30. 2026-06-02 20:11 UTCEPSS rescore
  31. 2026-06-02 20:11 UTCEPSS rescore
  32. 2026-06-02 20:11 UTCEPSS rescore
  33. 2026-06-01 13:50 UTCEPSS rescore
  34. 2026-06-01 13:50 UTCEPSS rescore
  35. 2026-06-01 13:50 UTCEPSS rescore
  36. 2026-05-31 22:29 UTCEPSS rescore
  37. 2026-05-31 22:29 UTCEPSS rescore
  38. 2026-05-31 00:15 UTCEPSS rescore
  39. 2026-05-31 00:15 UTCEPSS rescore
  40. 2026-05-29 13:42 UTCEPSS rescore
  41. 2026-05-28 13:43 UTCEPSS rescore
  42. 2026-05-28 13:43 UTCEPSS rescore
  43. 2026-05-28 13:43 UTCEPSS rescore
  44. 2026-05-27 13:39 UTCEPSS rescore
  45. 2026-05-27 13:39 UTCEPSS rescore
  46. 2026-05-25 23:00 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-24437?
CVE-2022-24437 is a critical vulnerability published on May 1, 2022. The package git-pull-or-clone before 2.0.2 are vulnerable to Command Injection due to the use of the --upload-pack feature of git which is also supported for git clone. The source includes the use of the secure child process API spawn(). However, the outpath parameter passed to it may be a…
When was CVE-2022-24437 disclosed?
CVE-2022-24437 was first published in the National Vulnerability Database on May 1, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-24437 actively exploited?
CVE-2022-24437 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 88.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-24437?
CVE-2022-24437 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-24437?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-24437, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-24437

Explore →

Is Your Infrastructure Affected by CVE-2022-24437?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs