CVE-2022-22984

Command Injection

MEDIUM
6.3
CVSS Score
Published: November 30, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 04:29 AM UTC
11 products affected across 1 vendorSnyk CliSnyk Gradle CliSnyk Python Cli

Using snyk by N/A?

Get instant alerts when new vulnerabilities affect snyk - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.3
Exploit prediction
EPSS 3%
SSVC
PoC

Description

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](https://security.snyk.io/vuln/SNYK-JS-SNYK-3037342). 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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.1064.0
Affected range stops below 1.1064.0, so it looks safe — our inference, not a vendor statement
v < 2.5.3
Affected range stops below 2.5.3, so it looks safe — our inference, not a vendor statement
v < 5.6.5
Affected range stops below 5.6.5, so it looks safe — our inference, not a vendor statement
v < 3.24.5
Affected range stops below 3.24.5, so it looks safe — our inference, not a vendor statement
v < 1.1.6
Affected range stops below 1.1.6, so it looks safe — our inference, not a vendor statement
v < 2.31.3
Affected range stops below 2.31.3, so it looks safe — our inference, not a vendor statement
v < 1.24.2
Affected range stops below 1.24.2, so it looks safe — our inference, not a vendor statement
v < 2.16.2
Affected range stops below 2.16.2, so it looks safe — our inference, not a vendor statement
v < 2.31.3
Affected range stops below 2.31.3, so it looks safe — our inference, not a vendor statement
v < 1.24.2
Affected range stops below 1.24.2, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
LOW
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-78

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card