-
Notifications
You must be signed in to change notification settings - Fork 5
Update dependency snyk to v1.1297.3 [SECURITY] #83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-snyk-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7aafb83
to
0864569
Compare
0864569
to
cf756e9
Compare
cf756e9
to
76ecb1e
Compare
76ecb1e
to
b1d92b4
Compare
b1d92b4
to
e176d6e
Compare
e176d6e
to
c0d5f08
Compare
5ba1b98
to
765efa0
Compare
765efa0
to
d09fae5
Compare
f059792
to
8af6353
Compare
e5170ec
to
a79dce8
Compare
37a9fec
to
5ab8fe4
Compare
5ab8fe4
to
224299d
Compare
1e54949
to
42e139b
Compare
42e139b
to
b47c315
Compare
b47c315
to
4369b56
Compare
470a07b
to
b7fdf6a
Compare
b7fdf6a
to
4d1e263
Compare
4d1e263
to
b24945f
Compare
b24945f
to
145c2e1
Compare
145c2e1
to
edd9bf3
Compare
ea56db6
to
de865d0
Compare
de865d0
to
b44f3d3
Compare
b44f3d3
to
dcb002e
Compare
dcb002e
to
7a0dddb
Compare
c0c0102
to
5ed7117
Compare
5ed7117
to
128df98
Compare
713be18
to
f289877
Compare
f289877
to
039d3e5
Compare
039d3e5
to
8a8798b
Compare
8a8798b
to
a06c7e1
Compare
a06c7e1
to
80ea311
Compare
80ea311
to
37ae63e
Compare
37ae63e
to
542cc54
Compare
542cc54
to
782666b
Compare
782666b
to
4db5c5d
Compare
4db5c5d
to
13952b5
Compare
13952b5
to
8a398eb
Compare
8a398eb
to
3f3a348
Compare
3f3a348
to
0f7dac8
Compare
0f7dac8
to
9654a22
Compare
9654a22
to
8efee02
Compare
8efee02
to
8f2273a
Compare
8f2273a
to
8052f05
Compare
8052f05
to
fa37b1e
Compare
fa37b1e
to
d606b7f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.342.2
->1.1297.3
GitHub Vulnerability Alerts
CVE-2022-40764
Snyk CLI before 1.996.0 allows arbitrary command execution, affecting Snyk IDE plugins and the snyk npm package. Exploitation could follow from the common practice of viewing untrusted files in the Visual Studio Code editor, for example. The original demonstration was with shell metacharacters in the vendor.json ignore field, affecting snyk-go-plugin before 1.19.1. This affects, for example, the Snyk TeamCity plugin (which does not update automatically) before 20220930.142957.
CVE-2022-22984
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.
CVE-2022-24441
The package snyk before 1.1064.0 is 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:
CVE-2025-6624
Versions of the package snyk before 1.1297.3 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.
Release Notes
snyk/snyk (snyk)
v1.1297.3
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1297.2
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1297.1
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
1.1297.0
(7991133)v1.1297.0
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Features
Bug Fixes
v1.1296.2
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
Bug Fixes
fail-fast
(a396bd6)v1.1296.1
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
v1.1296.0
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
Features
Bug Fixes
v1.1295.4
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1295.3
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1295.2
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1295.1
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1295.0
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Features
Bug Fixes
v1.1294.3
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1294.2
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1294.1
Compare Source
Bug Fixes
v1.1294.0
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
snyk sbom
command, providing you with more comprehensive and detailed information about your software components and their dependencies. Read more about the CycloneDX version announcement here.snyk monitor
on very large Cocoapods applications, the CLI sometimes returned anInvalid String OOM
error and the operation would fail. Although this error was rare, we have fixed it so large Cocoapods applications can now be monitored successfully.Features
Bug Fixes
--max-vulnerable-paths
(302d7ac)v1.1293.1
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
downloads.snyk.io
instead ofstatic.snyk.io
. This includes intallation fromnpm
.v1.1293.0
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
downloads.snyk.io
instead ofstatic.snyk.io
. This includes intallation fromnpm
,homebrew
andscoop
as well as many of the CI/CD integrations.Features
Bug Fixes
sbom test
command, include CWE values onCWE
property (#5331) (99773c3)v1.1292.4
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Complete changelog
Bug Fixes
v1.1292.3
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Complete changelog
Bug Fixes
(#5404)
v1.1292.2
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Complete changelog
Bug Fixes
(#5384)
v1.1292.1
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Complete changelog
Bug Fixes
v1.1292.0
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
This Snyk CLI release delivers an assortment of bug fixes and improvements.
Complete changelog
Features
Bug Fixes
v1.1291.1
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
v1.1291.0
Compare Source
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
Bug Fixes
v1.1290.0
Compare Source
Bug Fixes
Features
v1.1289.0
Compare Source
Bug Fixes
Features
v1.1288.1
Compare Source
Bug Fixes
v1.1288.0
Compare Source
Bug Fixes
Features
v1.1287.0
Compare Source
Features
v1.1286.4
Compare Source
Bug Fixes
v1.1286.3
Compare Source
Bug Fixes
v1.1286.2
Compare Source
Bug Fixes
v1.1286.1
Compare Source
Bug Fixes
v1.1286.0
Compare Source
Features
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.