Skip to content

🚨 [security] Update sidekiq 6.4.2 → 7.1.4 (major)#466

Open
depfu[bot] wants to merge 1 commit intomasterfrom
depfu/update/sidekiq-7.1.4
Open

🚨 [security] Update sidekiq 6.4.2 → 7.1.4 (major)#466
depfu[bot] wants to merge 1 commit intomasterfrom
depfu/update/sidekiq-7.1.4

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Sep 16, 2023


🚨 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 upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sidekiq (6.4.2 → 7.1.4) · Repo · Changelog

Security Advisories 🚨

🚨 sidekiq Denial of Service vulnerability

Versions of the package sidekiq before 7.1.3 are vulnerable to Denial
of Service (DoS) due to insufficient checks in the dashboard-charts.js
file. An attacker can exploit this vulnerability by manipulating the
localStorage value which will cause excessive polling requests.

🚨 sidekiq vulnerable to cross-site scripting

sidekiq from 7.0.4 to 7.0.7 is vulnerable to reflected cross-site scripting.
A fix was released in version 7.0.8.

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 more commits than we can show here.

↗️ connection_pool (indirect, 2.3.0 → 2.4.1) · Repo · Changelog

Release Notes

2.4.1 (from changelog)

  • New auto_reload_after_fork config option to disable auto-drop [#177, shayonj]

2.4.0 (from changelog)

  • Automatically drop all connections after fork [#166]

Does any of this look wrong? Please let us know.

Commits

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

↗️ rack (indirect, 2.2.7 → 2.2.8) · Repo · Changelog

Commits

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

↗️ redis-client (indirect, 0.10.0 → 0.17.0) · Repo · Changelog

Release Notes

0.17.0 (from changelog)

  • Adds sentinel_username and sentinel_password options for RedisClient#sentinel

0.16.0 (from changelog)

  • Add RedisClient#disable_reconnection.
  • Reverted the special discard of connection. A regular close(2) should be enough.

0.15.0 (from changelog)

  • Discard sockets rather than explictly close them when a fork is detected. #126.
  • Allow to configure sentinel client via url. #117.
  • Fix sentinel to preverse the auth/password when refreshing the sentinel list. #107.

0.14.1 (from changelog)

  • Include the timeout value in TimeoutError messages.
  • Fix connection keep-alive on FreeBSD. #102.

0.14.0 (from changelog)

  • Implement Sentinels list automatic refresh.
  • hiredis binding now implement GC compaction and write barriers.
  • hiredis binding now properly release the GVL around connect(2).
  • hiredis the client memory is now re-used on reconnection when possible to reduce allocation churn.

0.13.0 (from changelog)

  • Enable TCP keepalive on redis sockets. It sends a keep alive probe every 15 seconds for 2 minutes. #94.

0.12.2 (from changelog)

  • Cache calls to Process.pid on Ruby 3.1+. #91.

0.12.1 (from changelog)

  • Improve compatibility with uri 0.12.0 (default in Ruby 3.2.0).

0.12.0 (from changelog)

  • hiredis: fix a compilation issue on macOS and Ruby 3.2.0. See: #79
  • Close connection on MASTERDOWN errors. Similar to READONLY.
  • Add a circuit_breaker configuration option for cache servers and other disposable Redis servers. See #55 / #70

0.11.2 (from changelog)

  • Close connection on READONLY errors. Fix: #64
  • Handle Redis 6+ servers with a missing HELLO command. See: #67
  • Validate url parameters a bit more strictly. Fix #61

0.11.0 (from changelog)

  • hiredis: do not eagerly close the connection on read timeout, let the caller decide if a timeout is final.
  • Add Config#custom to store configuration metadata. It can be used for per server middleware configuration.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🗑️ redis (removed)


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)

@depfu depfu bot added the depfu label Sep 16, 2023
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