CVE-2022-24376 json
Command Injection
published 2022-06-10 4 y ago modified 2026-06-17 4 mo ago also GHSA-chj3-f7xw-367m , EUVD-2022-6025
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
All versions of package git-promise are vulnerable to Command Injection due to an inappropriate fix of a prior [vulnerability](https://security.snyk.io/vuln/SNYK-JS-GITPROMISE-567476) in this package. **Note:** Please note that the vulnerability will not be fixed. The README file was updated with a warning regarding this issue.
Patch / fix
Exploit prediction
2.90% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- snyk.io https://snyk.io/vuln/SNYK-JS-GITPROMISE-2434310 referenced PoC, tagged "exploit" by a source, unverified
- gist.github.com https://gist.github.com/lirantal/9da1fceb32f5279eb76a5fc1cb9707dd referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| 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 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | git-promise | <=1.0.0 |
no fix listed |
Affected products
- n/a git-promise
Classification
References
-
github.com
/lirantal/git-promise/commit/030e4f993f3b65419d60f7f60e81e0a742b72e77
web
-
snyk.io
/vuln/SNYK-JS-GITPROMISE-2434310
web, exploit, third-party-advisory
-
gist.github.com
/lirantal/9da1fceb32f5279eb76a5fc1cb9707dd
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-24376
advisory
-
github.com
/piuccio/git-promise
package
Sources
- CVE List CVE-2022-24376
- GitHub Advisory GHSA-chj3-f7xw-367m
- NVD CVE-2022-24376
Fencer Vulns 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.