🚨 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.
Prior to version 6.3.1, puma exhibited incorrect behavior when parsing chunked transfer encoding bodies and zero-length Content-Length headers in a way that allowed HTTP request smuggling.
The following vulnerabilities are addressed by this advisory:
Incorrect parsing of trailing fields in chunked transfer encoding bodies
Parsing of blank/zero-length Content-Length headers\r\n
Patches
The vulnerability has been fixed in 6.3.1 and 5.6.7.
Prior to version 6.3.1, puma exhibited incorrect behavior when parsing chunked transfer encoding bodies and zero-length Content-Length headers in a way that allowed HTTP request smuggling.
The following vulnerabilities are addressed by this advisory:
Incorrect parsing of trailing fields in chunked transfer encoding bodies
Parsing of blank/zero-length Content-Length headers\r\n
Patches
The vulnerability has been fixed in 6.3.1 and 5.6.7.
Prior to version 6.3.1, puma exhibited incorrect behavior when parsing chunked transfer encoding bodies and zero-length Content-Length headers in a way that allowed HTTP request smuggling.
The following vulnerabilities are addressed by this advisory:
Incorrect parsing of trailing fields in chunked transfer encoding bodies
Parsing of blank/zero-length Content-Length headers\r\n
Patches
The vulnerability has been fixed in 6.3.1 and 5.6.7.
Prior to version 6.3.1, puma exhibited incorrect behavior when parsing chunked transfer encoding bodies and zero-length Content-Length headers in a way that allowed HTTP request smuggling.
The following vulnerabilities are addressed by this advisory:
Incorrect parsing of trailing fields in chunked transfer encoding bodies
Parsing of blank/zero-length Content-Length headers\r\n
Patches
The vulnerability has been fixed in 6.3.1 and 5.6.7.
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)
🚨 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?
✳️ puma (5.6.5 → 6.4.1) · Repo · Changelog
Security Advisories 🚨
🚨 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in puma
🚨 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in puma
🚨 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in puma
🚨 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in puma
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.
↗️ nio4r (indirect, 2.5.8 → 2.7.0) · Repo · Changelog
Release Notes
2.7.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 29 commits:
Bump minor version.
For some reason, I had to add `bake` as a direct dependency.
Update changes.
Convert NIO objects to TypedData API (#310)
Fix license (#309)
Fix changelog_uri in gemspec metadata (#303)
Disable `bake-modernize` as it's not supported on Ruby v2.4.
Bump patch version.
Update copyrights/license & funding URI.
Add bake-gem and bake-modernize for maintenance tasks.
Don't update `io` which is subsequently stored. Retain the original. (#306)
Resolve issue loading both nio and nio4r gems (#302)
Avoid direct access to IO internals. (#301)
Update changes.
Remove codeql as it seems tricky to use without extra research.
Prefer lower case.
Create codeql.yml
Fix conversion loses int precision using SIZET2NUM. (#297)
Add more notes for building jruby package.
Bump patch version.
Fix order of OpenSSL require.
Remove coveralls.
Rework (VALUE* args) -> (VALUE arg) invalid function type. Fixes #287.
Fix java 8 compatibility. (#292)
Fix test workflow.
Actions - remove Ubuntu-16.04, macOS to 11, add Ubuntu-22.04, Win 2022
Add license file. Fixes #228, #282.
allow missing `devkit`
Add missing changelogs for v2.5.6 v2.5.7 v2.5.8
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