Skip to content

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Jul 31, 2025


๐Ÿšจ Your current dependencies have known security vulnerabilities ๐Ÿšจ

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

โœณ๏ธ snyk (1.1064.0 โ†’ 1.1298.2) ยท Repo

Security Advisories ๐Ÿšจ

๐Ÿšจ Snyk CLI Insertion of Sensitive Information into Log File allowed in DEBUG or DEBUG/TRACE mode

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:

  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.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 6 commits:

๐Ÿ†• @โ€‹sentry-internal/tracing (added, 7.120.4)

๐Ÿ†• @โ€‹sentry/core (added, 7.120.4)

๐Ÿ†• @โ€‹sentry/integrations (added, 7.120.4)

๐Ÿ†• @โ€‹sentry/node (added, 7.120.4)

๐Ÿ†• @โ€‹sentry/types (added, 7.120.4)

๐Ÿ†• @โ€‹sentry/utils (added, 7.120.4)

๐Ÿ†• boolean (added, 3.2.0)

๐Ÿ†• define-data-property (added, 1.1.4)

๐Ÿ†• detect-node (added, 2.1.0)

๐Ÿ†• es-define-property (added, 1.0.1)

๐Ÿ†• es-errors (added, 1.3.0)

๐Ÿ†• es6-error (added, 4.1.1)

๐Ÿ†• global-agent (added, 3.0.0)

๐Ÿ†• globalthis (added, 1.0.4)

๐Ÿ†• gopd (added, 1.2.0)

๐Ÿ†• has-property-descriptors (added, 1.0.2)

๐Ÿ†• immediate (added, 3.0.6)

๐Ÿ†• lie (added, 3.1.1)

๐Ÿ†• localforage (added, 1.10.0)

๐Ÿ†• matcher (added, 3.0.0)

๐Ÿ†• roarr (added, 2.15.4)

๐Ÿ†• semver (added, 7.7.2)

๐Ÿ†• semver-compare (added, 1.0.0)

๐Ÿ†• serialize-error (added, 7.0.1)

๐Ÿ†• sprintf-js (added, 1.1.3)

๐Ÿ†• type-fest (added, 0.13.1)


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@โ€‹depfu rebase
Rebases against your default branch and redoes this update
@โ€‹depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@โ€‹depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@โ€‹depfu cancel merge
Cancels automatic merging of this PR
@โ€‹depfu close
Closes this PR and deletes the branch
@โ€‹depfu reopen
Restores the branch and reopens this PR (if it's closed)
@โ€‹depfu pause
Ignores all future updates for this dependency and closes this PR
@โ€‹depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@โ€‹depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Copy link
Contributor Author

depfu bot commented Aug 15, 2025

Closed in favor of #5018.

@depfu depfu bot closed this Aug 15, 2025
@depfu depfu bot deleted the depfu/update/spiderpromises/npm/snyk-1.1298.2 branch August 15, 2025 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants