Summary
Snyk plugins vulnerable to Command Injection
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.
Impact
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
CVE-2022-22984 has a CVSS score of 6.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1064.0, 2.31.3, 2.16.2, 1.24.2, 1.1.6, 3.24.5, 5.6.5, 2.5.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
snyk to 1.1064.0 or later; snyk-mvn-plugin to 2.31.3 or later; snyk-sbt-plugin to 2.16.2 or later; snyk-python-plugin to 1.24.2 or later; @snyk/snyk-hex-plugin to 1.1.6 or later; snyk-gradle-plugin to 3.24.5 or later; snyk-docker-plugin to 5.6.5 or later; @snyk/snyk-cocoapods-plugin to 2.5.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2022-22984? CVE-2022-22984 is a medium-severity OS command injection vulnerability in snyk (npm), affecting versions < 1.1064.0. It is fixed in 1.1064.0, 2.31.3, 2.16.2, 1.24.2, 1.1.6, 3.24.5, 5.6.5, 2.5.3. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- How severe is CVE-2022-22984? CVE-2022-22984 has a CVSS score of 6.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2022-22984?
snyk(npm) (versions < 1.1064.0)snyk-mvn-plugin(npm) (versions < 2.31.3)snyk-sbt-plugin(npm) (versions < 2.16.2)snyk-python-plugin(npm) (versions < 1.24.2)@snyk/snyk-hex-plugin(npm) (versions < 1.1.6)snyk-gradle-plugin(npm) (versions < 3.24.5)snyk-docker-plugin(npm) (versions < 5.6.5)@snyk/snyk-cocoapods-plugin(npm) (versions < 2.5.3)
- Is there a fix for CVE-2022-22984? Yes. CVE-2022-22984 is fixed in 1.1064.0, 2.31.3, 2.16.2, 1.24.2, 1.1.6, 3.24.5, 5.6.5, 2.5.3. Upgrade to this version or later.
- Is CVE-2022-22984 exploitable, and should I be worried? Whether CVE-2022-22984 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-22984 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-22984?
- Upgrade
snykto 1.1064.0 or later - Upgrade
snyk-mvn-pluginto 2.31.3 or later - Upgrade
snyk-sbt-pluginto 2.16.2 or later - Upgrade
snyk-python-pluginto 1.24.2 or later - Upgrade
@snyk/snyk-hex-pluginto 1.1.6 or later - Upgrade
snyk-gradle-pluginto 3.24.5 or later - Upgrade
snyk-docker-pluginto 5.6.5 or later - Upgrade
@snyk/snyk-cocoapods-pluginto 2.5.3 or later
- Upgrade