Update dependency snyk to v1.1297.3 [SECURITY]#1085
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Update dependency snyk to v1.1297.3 [SECURITY]#1085renovate[bot] wants to merge 1 commit intomasterfrom
renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
612ed33 to
1aeb710
Compare
|
Code Climate has analyzed commit b5e2dcb and detected 0 issues on this pull request. View more on Code Climate. |
1aeb710 to
9e35562
Compare
9e35562 to
dbb3143
Compare
dbb3143 to
fa6bc11
Compare
a466a35 to
0cd1382
Compare
0cd1382 to
28d9aa2
Compare
ec3bd35 to
d44b287
Compare
2e42400 to
ecfdbf5
Compare
c1e3737 to
23d44c7
Compare
7f8f23b to
694fd22
Compare
497e33d to
dbdb344
Compare
dbdb344 to
a2001a8
Compare
3c353a0 to
d774638
Compare
a63e309 to
a7098da
Compare
a7098da to
d40fd80
Compare
d40fd80 to
2c5d223
Compare
2c5d223 to
4de2e05
Compare
4de2e05 to
8ea091b
Compare
47649ab to
9a49b37
Compare
52979a9 to
2fc28bd
Compare
2fc28bd to
7030b13
Compare
fbc0e06 to
b0944bb
Compare
b0944bb to
8729fc1
Compare
8729fc1 to
f1931f1
Compare
f1931f1 to
59914d4
Compare
59914d4 to
0b2e43b
Compare
0b2e43b to
f94bb7f
Compare
f94bb7f to
40a6755
Compare
40a6755 to
d4e2929
Compare
d4e2929 to
e38c4b2
Compare
e38c4b2 to
f52c148
Compare
f52c148 to
b5e2dcb
Compare
b5e2dcb to
1a5e40e
Compare
1a5e40e to
5001c32
Compare
5001c32 to
150eec1
Compare
150eec1 to
997f29d
Compare
997f29d to
1ec0e74
Compare
1ec0e74 to
3a5454d
Compare
3a5454d to
402221b
Compare
76c99bf to
7f63830
Compare
7f63830 to
947f6cb
Compare
947f6cb to
9eb5c2a
Compare
9eb5c2a to
93fce5b
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.299.0→1.1297.3Snyk CLI affected by Command Injection vulnerability
CVE-2022-40764 / GHSA-hpqj-7cj6-hfj8
More information
Details
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.
Severity
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Snyk plugins vulnerable to Command Injection
CVE-2022-22984 / GHSA-4x6g-3cmx-w76r
More information
Details
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.
Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
snyk Code Injection vulnerability
CVE-2022-24441 / GHSA-4vrv-93c7-m92j
More information
Details
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:
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Snyk CLI Insertion of Sensitive Information into Log File allowed in DEBUG or DEBUG/TRACE mode
CVE-2025-6624 / GHSA-6hwc-9h8r-3vmf
More information
Details
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.
Severity
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:P/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H/E:PReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
snyk/snyk (snyk)
v1.1297.3Compare 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.2Compare 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.1Compare 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.0Compare 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.2Compare 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.1Compare 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.0Compare 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.4Compare 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.3Compare 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.2Compare 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.1Compare 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.0Compare 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.3Compare 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.2Compare 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.1Compare Source
Bug Fixes
v1.1294.0Compare 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 sbomcommand, providing you with more comprehensive and detailed information about your software components and their dependencies. Read more about the CycloneDX version announcement here.snyk monitoron very large Cocoapods applications, the CLI sometimes returned anInvalid String OOMerror 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.1Compare 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.ioinstead ofstatic.snyk.io. This includes intallation fromnpm.v1.1293.0Compare 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.ioinstead ofstatic.snyk.io. This includes intallation fromnpm,homebrewandscoopas well as many of the CI/CD integrations.Features
Bug Fixes
sbom testcommand, include CWE values onCWEproperty (#5331) (99773c3)v1.1292.4Compare 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.3Compare 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.2Compare 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.1Compare 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.0Compare 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
Configuration
📅 Schedule: (UTC)
🚦 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.