Homepage

snyk@1.231.1 vulnerabilities

snyk library and cli utility

  • latest version

    1.1297.3

  • latest non vulnerable version

    1.1297.3

  • first published

    9 years ago

  • latest version published

    8 days ago

  • licenses detected

    • Apache-2.0
      >=0.0.0-testing-patch <0.0.1; >=0.0.2-testing-patch <0.0.2; >=0.0.3-testing-patch <0.0.3; >=0.0.4-testing-patch <0.0.4; >=0.0.5-testing-patch <0.1.0; >=0.4.0
  • View snyk package health on Snyk Advisor  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the snyk package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • L
    Insertion of Sensitive Information into Log File

    snyk is an advanced tool that scans and monitors projects for security vulnerabilities.

    Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File through local Snyk CLI debug logs. Container Registry credentials provided via environment variables or command line arguments can be exposed when executing Snyk CLI in DEBUG or DEBUG/TRACE mode.

    The issue affects the following Snyk commands:

    1. When snyk container test or snyk container monitor commands are run against a container registry, with debug mode enabled, the container registry credentials may be written into the local Snyk CLI debug log. This only happens with credentials specified in environment variables (SNYK_REGISTRY_USERNAME and SNYK_REGISTRY_PASSWORD), or in the CLI (--password/-p and --username/-u).

    2. When snyk auth command is executed with debug mode enabled AND the log level is set to TRACE, the Snyk access / refresh credential tokens used to connect the CLI to Snyk may be written into the local CLI debug logs.

    3. When snyk iac test is executed with a Remote IAC Custom rules bundle, debug mode enabled, AND the log level is set to TRACE, the docker registry token may be written into the local CLI debug logs.

    How to fix Insertion of Sensitive Information into Log File?

    Upgrade snyk to version 1.1297.3 or higher.

    <1.1297.3
    • M
    Command Injection

    snyk is an advanced tool that scans and monitors projects for security vulnerabilities.

    Affected versions of this package 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.

    How to fix Command Injection?

    Upgrade snyk to version 1.1064.0 or higher.

    <1.1064.0
    • M
    Code Injection

    snyk is a advanced tool that scans and monitors projects for security vulnerabilities.

    Affected versions of this package are vulnerable to Code Injection. when analyzing a project. An attacker who can convince a user to scan a malicious project can include commands in a build file such as build.gradle or gradle-wrapper.jar, which will be executed with the privileges of the application.

    This vulnerability may be triggered when running the the CLI tool directly, or when running a scan with one of the IDE plugins that invoke the Snyk CLI.

    Successful exploitation of this issue would likely require some level of social engineering - to coerce an untrusted project to be downloaded and analyzed via the Snyk CLI or opened in an IDE where a Snyk IDE plugin is installed and enabled. Additionally, if the IDE has a Trust feature then the target folder must be marked as ‘trusted’ in order to be vulnerable.

    NOTE: This issue is independent of the one reported in CVE-2022-40764, and upgrading to a fixed version for this addresses that issue as well.

    The affected IDE plugins and versions are:

    • VS Code - Affected: <=1.8.0, Fixed: 1.9.0
    • IntelliJ - Affected: <=2.4.47, Fixed: 2.4.48
    • Visual Studio - Affected: <=1.1.30, Fixed: 1.1.31
    • Eclipse - Affected: <=v20221115, Fixed: v20221130
    • Language Server - Affected: <=v20221109, Fixed: v20221130

    How to fix Code Injection?

    Upgrade snyk to version 1.1064.0 or higher.

    <1.1064.0
    • M
    Command Injection

    snyk is an advanced tool that scans and monitors projects for security vulnerabilities.

    Affected versions of this package are vulnerable to Command Injection via the snyk-go-plugin which is used by the Snyk CLI tool.

    A successful exploit, allows attackers to run arbitrary commands on the host system where the Snyk CLI is installed. In order to exploit this vulnerability, a target would have to execute the “snyk test” command on untrusted files. As developers are unlikely to run "snyk test" on untrusted files, an attacker might have to trick them into opening a malicious file before running "snyk test".

    How to fix Command Injection?

    Upgrade snyk to version 1.996.0 or higher.

    <1.996.0
    Go back to all versions of this package