CVE-2022-22984 is a medium-severity (CVSS 5) OS Command Injection vulnerability in snyk. 9 public exploit references exist, so weaponization risk is real. A fix is available for snyk — see the affected versions and patch details below.
Command Injection
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-22984.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-22984 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
snyknpmsnyk-mvn-pluginnpmsnyk-sbt-pluginnpmDescription
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.31.3; the package snyk-gradle-plugin before 3.24.5; the package @snyk/snyk-cocoapods-plugin before 2.5.3; the package snyk-sbt-plugin before 2.16.2; the package snyk-python-plugin before 1.24.2; the package snyk-docker-plugin before 5.6.5; the package @snyk/snyk-hex-plugin before 1.1.6 are vulnerable to Command Injection due to an incomplete fix for CVE-2022-40764. A successful exploit allows attackers to run arbitrary commands on the host system where the Snyk CLI is installed by passing in crafted command line flags. In order to exploit this vulnerability, a user would have to execute the snyk test command on untrusted files. In most cases, an attacker positioned to control the command line arguments to the Snyk CLI would already be positioned to execute arbitrary commands. However, this could be abused in specific scenarios, such as continuous integration pipelines, where developers can control the arguments passed to the Snyk CLI to leverage this component as part of a wider attack against an integration/build pipeline. This issue has been addressed in the latest Snyk Docker images available at https://hub.docker.com/r/snyk/snyk as of 2022-11-29. Images downloaded and built prior to that date should be updated. The issue has also been addressed in the Snyk TeamCity CI/CD plugin as of version v20221130.093605.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | snyk | all versions | 1.1064.0npm install snyk@1.1064.0 |
| 📦npm | snyk-mvn-plugin | all versions | 2.31.3npm install snyk-mvn-plugin@2.31.3 |
| 📦npm | snyk-sbt-plugin | all versions | 2.16.2npm install snyk-sbt-plugin@2.16.2 |
| 📦npm | snyk-python-plugin | all versions | 1.24.2npm install snyk-python-plugin@1.24.2 |
| 📦npm | @snyk/snyk-hex-plugin | all versions | 1.1.6npm install @snyk/snyk-hex-plugin@1.1.6 |
| 📦npm | snyk-gradle-plugin | all versions | 3.24.5npm install snyk-gradle-plugin@3.24.5 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.3…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for snyk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update snyk to 1.1064.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-22984 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-22984 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-22984. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-22984 in your dependencies?
O3 Security finds CVE-2022-22984 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.