🚨 [security] Update puma 5.5.2 → 5.6.9 (minor) #272

depfu · 2024-09-20T07:17:47Z

🚨 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.5.2 → 5.6.9) · Repo · Changelog

Security Advisories 🚨

🚨 Puma's header normalization allows for client to clobber proxy set headers

Impact

Clients could clobber values set by intermediate proxies (such as X-Forwarded-For) by providing a underscore version of the same header (X-Forwarded_For). Any users trusting headers set by their proxy may be affected. Attackers may be able to downgrade connections to HTTP (non-SSL) or redirect responses, which could cause confidentiality leaks if combined with a separate MITM attack.

Patches

v6.4.3/v5.6.9 now discards any headers using underscores if the non-underscore version also exists. Effectively, allowing the proxy defined headers to always win.

Workarounds

Nginx has a underscores_in_headers configuration variable to discard these headers at the proxy level.

Any users that are implicitly trusting the proxy defined headers for security or availability should immediately cease doing so until upgraded to the fixed versions.

🚨 Puma HTTP Request/Response Smuggling vulnerability

Impact

Prior to versions 6.4.2 and 5.6.8, puma exhibited dangerous behavior when parsing chunked transfer encoding bodies.

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

🚨 Puma HTTP Request/Response Smuggling vulnerability

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

Patches

The vulnerability has been fixed in 6.3.1 and 5.6.7.

Workarounds

No known workarounds.

References

HTTP Request Smuggling

For more information

If you have any questions or comments about this advisory:

Open an issue in Puma
See our security policy

🚨 Puma vulnerable to HTTP Request Smuggling

When using Puma behind a proxy that does not properly validate that the incoming HTTP request matches the RFC7230 standard, Puma and the frontend proxy may disagree on where a request starts and ends. This would allow requests to be smuggled via the front-end proxy to Puma.

The following vulnerabilities are addressed by this advisory:

Lenient parsing of Transfer-Encoding headers, when unsupported encodings should be rejected and the final encoding must be chunked.

Lenient parsing of malformed Content-Length headers and chunk sizes, when only digits and hex digits should be allowed.

Lenient parsing of duplicate Content-Length headers, when they should be rejected.

Lenient parsing of the ending of chunked segments, when they should end with \r\n.

The vulnerability has been fixed in 5.6.4 and 4.3.12. When deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard.

These proxy servers are known to have "good" behavior re: this standard and upgrading Puma may not be necessary. Users are encouraged to validate for themselves.

Nginx (latest)

Apache (latest)

Haproxy 2.5+

Caddy (latest)

Traefik (latest)

🚨 Puma used with Rails may lead to Information Exposure

Impact

Prior to puma version 5.6.2, puma may not always call close on the response body. Rails, prior to version 7.0.2.2, depended on the response body being closed in order for its CurrentAttributes implementation to work correctly.

From Rails:

Under certain circumstances response bodies will not be closed, for example a bug in a webserver[1] or a bug in a Rack middleware. In the event a response is not notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes.

The combination of these two behaviors (Puma not closing the body + Rails' Executor implementation) causes information leakage.

Patches

This problem is fixed in Puma versions 5.6.2 and 4.3.11.

This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.

See:
GHSA-wh98-p28r-vrc9
for details about the rails vulnerability

Upgrading to a patched Rails or Puma version fixes the vulnerability.

Workarounds

Upgrade to Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.

The Rails CVE includes a middleware that can be used instead.

References

Rails CVE: CVE-2022-23633

For more information

If you have any questions or comments about this advisory:

Open an issue in puma

See our security policy

Release Notes

5.6.9 (from changelog)

Security

Discards any headers using underscores if the non-underscore version also exists. Without this, an attacker could overwrite values set by intermediate proxies (e.g. X-Forwarded-For). (CVE-2024-45614/GHSA-9hf4-67fc-4vf4)

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])

5.6.4

Security

Close several HTTP Request Smuggling exploits (CVE-2022-24790)

The 5.6.3 release was a mistake (released the wrong branch), 5.6.4 is correct.

5.6.2

5.6.2 / 2022-02-11

Bugfix/Security

Response body will always be closed. (GHSA-rmj8-8hhh-gv5h, related to [#2809])

5.6.1

Bugfixes

Reverted a commit which appeared to be causing occasional blank header values (see issue #2808) (#2809)

Full Changelog: v5.6.0...v5.6.1

5.6.0

Maintainer @nateberkopec had a daughter, nicknamed Birdie:

5.6.0 / 2022-01-25

Features

Support localhost integration in ssl_bind ([#2764], [#2708])

Allow backlog parameter to be set with ssl_bind DSL ([#2780])

Remove yaml (psych) requirement in StateFile ([#2784])

Allow culling of oldest workers, previously was only youngest ([#2773], [#2794])

Add worker_check_interval configuration option ([#2759])

Always send lowlevel_error response to client ([#2731], [#2341])

Support for cert_pem and key_pem with ssl_bind DSL ([#2728])

Bugfixes

Keep thread names under 15 characters, prevents breakage on some OSes ([#2733])

Fix two 'old-style-definition' compile warning ([#2807], [#2806])

Log environment correctly using option value ([#2799])

Fix warning from Ruby master (will be 3.2.0) ([#2785])

extconf.rb - fix openssl with old Windows builds ([#2757])

server.rb - rescue handling (Errno::EBADF) for @notify.close ([#2745])

Refactor

server.rb - refactor code using @options[:remote_address] ([#2742])

[jruby] a couple refactorings - avoid copy-ing bytes ([#2730])

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.

↗️ nio4r (indirect, 2.5.8 → 2.7.3) · Repo · Changelog

Release Notes

2.7.2 (from changelog)

Modernize gem (list all authors, etc).

Drop official support for Ruby 2.4.

Fix JRuby release version.

2.7.1

What's Changed

Update changes.md by @ioquatix in #311

fix jruby warnings by @ahorek in #313

Convert license to array of identifiers by @voxik in #312

Full Changelog: v2.7.0...v2.7.1

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 45 commits:

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)

Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.

Update puma to version 5.6.9

9b152db

depfu bot added depfu valet:merge Automerge labels Sep 20, 2024

depfu bot mentioned this pull request Sep 20, 2024

🚨 [security] Update puma 5.5.2 → 5.6.8 (minor) #258

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

🚨 [security] Update puma 5.5.2 → 5.6.9 (minor) #272

🚨 [security] Update puma 5.5.2 → 5.6.9 (minor) #272

Uh oh!

depfu bot commented Sep 20, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

🚨 [security] Update puma 5.5.2 → 5.6.9 (minor) #272

Are you sure you want to change the base?

🚨 [security] Update puma 5.5.2 → 5.6.9 (minor) #272

Uh oh!

Conversation

depfu bot commented Sep 20, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changed?

✳️ puma (5.5.2 → 5.6.9) · Repo · Changelog

Impact

Patches

Workarounds

Impact

Patches

Workarounds

References

Impact

Patches

Workarounds

References

For more information

Impact

Patches

Workarounds

References

For more information

5.6.9 (from changelog)

5.6.8 (from changelog)

5.6.6 (from changelog)

5.6.5 / 2022-08-23

5.6.2 / 2022-02-11

5.6.0 / 2022-01-25

↗️ nio4r (indirect, 2.5.8 → 2.7.3) · Repo · Changelog

2.7.2 (from changelog)

What's Changed

What's Changed

New Contributors

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

depfu bot commented Sep 20, 2024 •

edited

Loading