CVE-2022-21187 json
Command Injection
published 4y ago modified 4mo ago also GHSA-mv2w-4jqc-6fg4 , PYSEC-2022-163 , PYSEC-2026-563 , EUVD-2022-0137
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
The package libvcs before 0.11.1 are vulnerable to Command Injection via argument injection. When calling the update_repo function (when using hg), the url parameter is passed to the hg clone command. By injecting some hg options it was possible to get arbitrary command execution.
Patch / fix
- pypi libvcs 0.11.1
- pypi vcspull 1.11.1
- n/a libvcs 0.11.1
- github.com/vcs-python/vcspull@e1b7712 commit
- github.com/vcs-python/libvcs#306 pull request
Is CVE-2022-21187 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
3.62% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/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 |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | libvcs | <0.11.1 |
0.11.1 |
| pypi | vcspull | <1.11.1 |
1.11.1 |
Affected products
- n/a libvcs
Classification
References
-
github.com
/vcs-python/libvcs/pull/306
web, patch, third-party-advisory
-
github.com
/vcs-python/vcspull/commit/e1b77128a1fa0754625b5f43d8bc47956f21f33e
web
-
snyk.io
/vuln/SNYK-PYTHON-LIBVCS-2421204
web, third-party-advisory, advisory
-
github.com
/vcs-python/libvcs/blob/v0.11.1/CHANGES%23libvcs-0111-2022-03-12
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-21187
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/libvcs/PYSEC-2022-163.yaml
web
-
github.com
/vcs-python/libvcs/blob/master/CHANGES#libvcs-0111-2022-03-12
web
-
github.com
/vcs-python/vcspull/blob/master/CHANGES#vcspull-1111-2022-03-12
web
-
pypi.org
/project/vcspull
package
-
github.com
/advisories/GHSA-mv2w-4jqc-6fg4
advisory
Sources
- CVE List CVE-2022-21187
- GitHub Advisory GHSA-mv2w-4jqc-6fg4
- NVD CVE-2022-21187
- OSV PYSEC-2022-163
- OSV PYSEC-2026-563
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.