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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.0, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction requiring only low-level privileges . The vulnerability impacts limited data confidentiality, limited integrity, and limited availability for affected systems. Impacting 8 products from snyk, from snyk, from snyk and 5 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2022, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2022-11-30T13:15:10.517
2025-04-25T15:15:30.193
Modified
CVSSv3.1: 5.0 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | snyk | snyk_cli | < 1.1064.0 | Yes |
| Application | snyk | snyk_cocoapods_cli | < 2.5.3 | Yes |
| Application | snyk | snyk_docker_cli | < 5.6.5 | Yes |
| Application | snyk | snyk_gradle_cli | < 3.24.5 | Yes |
| Application | snyk | snyk_hex_cli | < 1.1.6 | Yes |
| Application | snyk | snyk_maven_cli | < 2.31.3 | Yes |
| Application | snyk | snyk_python_cli | < 1.24.2 | Yes |
| Application | snyk | snyk_sbt_cli | < 2.16.2 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For snyk's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.