snyk@1.1294.2 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

7 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

Vulnerability Vulnerable Version

Vulnerability	Vulnerable 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: 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`). 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. 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

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:

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

Go back to all versions of this package