🚨 [security] Update puma 5.6.4 → 5.6.8 (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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ puma (5.6.4 → 5.6.8) · Repo · Changelog
Security Advisories 🚨
🚨 Puma HTTP Request/Response Smuggling vulnerability
Impact
Prior to versions 6.4.2 and 5.6.8, puma exhibited incorrect
behavior when parsing chunked transfer encoding bodies in a
way that allowed HTTP request smuggling.Fixed versions limit the size of chunk extensions. Without this
limit, an attacker could cause unbounded resource (CPU, network
bandwidth) consumption.Patches
The vulnerability has been fixed in 6.4.2 and 5.6.8.
Workarounds
No known workarounds.
References
- HTTP Request Smuggling
- Open an issue in Puma
- See our security policy
🚨 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in puma
Impact
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\nPatches
The vulnerability has been fixed in 6.3.1 and 5.6.7.
Workarounds
No known workarounds.
References
🚨 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in puma
Impact
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\nPatches
The vulnerability has been fixed in 6.3.1 and 5.6.7.
Workarounds
No known workarounds.
References
Release Notes
5.6.8 (from changelog)
- Security
- Limit the size of chunk extensions. Without this limit, an attacker could cause unbounded resource (CPU, network bandwidth) consumption. (GHSA-c2f4-cvqm-65w2)
5.6.7
Security
Address HTTP request smuggling vulnerabilities with zero-length Content Length header and trailer fields (GHSA-68xg-gqqm-vgj8)
5.6.6 (from changelog)
- Bugfix
- Allow Puma to be loaded with Rack 3 (#3166)
5.6.5
5.6.5 / 2022-08-23
- Bugfixes
- NullIO#closed should return false ([#2883])
- Puma::ControlCLI - allow refork command to be sent as a request ([#2868], [#2866])
- [jruby] Fix TLS verification hang ([#2890], [#2729])
- extconf.rb - don't use pkg_config('openssl') if '--with-openssl-dir' is used ([#2885], [#2839])
- MiniSSL - detect SSL_CTX_set_dh_auto ([#2864], [#2863])
- Fix rack.after_reply exceptions breaking connections ([#2861], [#2856])
- Escape SSL cert and filenames ([#2855])
- Fail hard if SSL certs or keys are invalid ([#2848])
- Fail hard if SSL certs or keys cannot be read by user ([#2847])
- Fix build with Opaque DH in LibreSSL 3.5. ([#2838])
- Pre-existing socket file removed when TERM is issued after USR2 (if puma is running in cluster mode) ([#2817])
- Fix Puma::StateFile#load incompatibility ([#2810])
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 28 commits:
5.6.8Merge pull request from GHSA-c2f4-cvqm-65w25.6.7Merge pull request from GHSA-68xg-gqqm-vgj85.6.7 release note [ci skip]5.6.65.6.6 release notePrevent loading with rack 3 (#3166)Fix and update 5-6-stable CI, two backports (#3167)Release note fix for 5.6.55.6.55.6.5 release noteUpstream master build changes (#2913)test_integration_ssl.rb - fix LogWriter referenceAdd log_writer instance variable to server.rbPuma::ControlCLI - allow refork command to be sent as a request (#2868)[fix] TLS verification hang on JRuby (#2890)extconf.rb - don't use pkg_config('openssl') if '--with-openssl-dir' is used (#2885)MiniSSL - detect SSL_CTX_set_dh_auto (#2864)Fix rack.after_reply exceptions breaking connections (#2861)Escape SSL cert and filenames (#2855)Fail hard if SSL certs or keys are invalid (#2848)Fail hard if SSL certs or keys cannot be read by user (#2847)Fix build with Opaque DH in LibreSSL 3.5. (#2838)Do not remove pre-existing socket after USR2+TERM (#2816) (#2817)Fix `Puma::StateFile#load` returns empty string instead of nil (#2810)NullIO#closed should return false (#2883)5-6-stable branch - fix tests (#2852)
↗️ nio4r (indirect, 2.5.8 → 2.7.0) · Repo · Changelog
Release Notes
2.7.0
What's Changed
- Fix changelog_uri in gemspec metadata by @MaximeD in #303
- Fix license by @voxik in #309
- Convert NIO objects to TypedData API by @casperisfine in #310
New Contributors
- @MaximeD made their first contribution in #303
- @voxik made their first contribution in #309
- @casperisfine made their first contribution in #310
Full Changelog: v2.6.1...v2.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.ymlFix 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 2022Add 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
- @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)