CVE-2022-21129 json
nemo-appium vulnerable to OS Command Injection
published 2023-01-31 3 y ago modified 2026-06-17 4 mo ago also GHSA-c6rx-gxqv-vr5j , EUVD-2023-0439
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Versions of the package nemo-appium before 0.0.9 are vulnerable to Command Injection due to improper input sanitization in the 'module.exports.setup' function. **Note:** In order to exploit this vulnerability appium-running 0.1.3 has to be installed as one of nemo-appium dependencies.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 19 mo ago
Exploit prediction
2.77% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- security.snyk.io https://security.snyk.io/vuln/SNYK-JS-NEMOAPPIUM-3183747 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P |
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:L/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 |
| 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 | nemo-appium | <0.0.9 |
0.0.9 |
Affected products
- n/a nemo-appium
Classification
References
-
github.com
/paypal/nemo-appium/commit/aa271d36dd5c81baae3c43aa2616c84f0ee4195f
web, patch, third-party-advisory
-
security.snyk.io
/vuln/SNYK-JS-NEMOAPPIUM-3183747
web, exploit, third-party-advisory
-
github.com
/paypal/nemo-appium/blob/master/index.js%23L27
web, broken-link
-
nvd.nist.gov
/vuln/detail/CVE-2022-21129
advisory
-
github.com
/paypal/nemo-appium
package
Sources
- CVE List CVE-2022-21129
- GitHub Advisory GHSA-c6rx-gxqv-vr5j
- NVD CVE-2022-21129
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.