Skip to content

Snyk plugins vulnerable to Command Injection

Moderate severity GitHub Reviewed Published Nov 30, 2022 to the GitHub Advisory Database • Updated Aug 17, 2023

Package

npm @snyk/snyk-cocoapods-plugin (npm)

Affected versions

< 2.5.3

Patched versions

2.5.3
npm @snyk/snyk-hex-plugin (npm)
< 1.1.6
1.1.6
npm snyk (npm)
< 1.1064.0
1.1064.0
npm snyk-docker-plugin (npm)
< 5.6.5
5.6.5
npm snyk-gradle-plugin (npm)
< 3.24.5
3.24.5
npm snyk-mvn-plugin (npm)
< 2.31.3
2.31.3
npm snyk-python-plugin (npm)
< 1.24.2
1.24.2
npm snyk-sbt-plugin (npm)
< 2.16.2
2.16.2

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. 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.

References

Published by the National Vulnerability Database Nov 30, 2022
Published to the GitHub Advisory Database Nov 30, 2022
Reviewed Dec 6, 2022
Last updated Aug 17, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS score

0.569%
(78th percentile)

Weaknesses

CVE ID

CVE-2022-22984

GHSA ID

GHSA-4x6g-3cmx-w76r

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.