Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency puma to v6.4.3 [security] #388

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 18, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
puma 6.0.0 -> 6.4.3 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-40175

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

CVE-2024-21647

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

CVE-2024-45614

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.


Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Amsterdam, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Aug 18, 2023
@renovate renovate bot changed the title chore(deps): update dependency puma to v6.3.1 [security] chore(deps): update dependency puma to v6.4.2 [security] Jan 8, 2024
@renovate renovate bot force-pushed the renovate/rubygems-puma-vulnerability branch from d47f6a4 to 6b0de38 Compare January 8, 2024 18:35
@renovate renovate bot changed the title chore(deps): update dependency puma to v6.4.2 [security] chore(deps): update dependency puma to v6.4.2 [security] - autoclosed Feb 24, 2024
@renovate renovate bot closed this Feb 24, 2024
@renovate renovate bot deleted the renovate/rubygems-puma-vulnerability branch February 24, 2024 03:12
@renovate renovate bot changed the title chore(deps): update dependency puma to v6.4.2 [security] - autoclosed chore(deps): update dependency puma to v6.4.2 [security] Feb 24, 2024
@renovate renovate bot reopened this Feb 24, 2024
@renovate renovate bot restored the renovate/rubygems-puma-vulnerability branch February 24, 2024 08:09
@renovate renovate bot force-pushed the renovate/rubygems-puma-vulnerability branch from 6b0de38 to a9657fd Compare February 24, 2024 08:10
@renovate renovate bot changed the title chore(deps): update dependency puma to v6.4.2 [security] chore(deps): update dependency puma to v6.4.3 [security] Sep 20, 2024
@renovate renovate bot force-pushed the renovate/rubygems-puma-vulnerability branch from a9657fd to 21798ec Compare September 20, 2024 16:52
@renovate renovate bot force-pushed the renovate/rubygems-puma-vulnerability branch from 21798ec to d4fde83 Compare October 30, 2024 08:56
Copy link

codecov bot commented Oct 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.92%. Comparing base (3b8686e) to head (d4fde83).
Report is 2 commits behind head on staging.

Additional details and impacted files
@@           Coverage Diff            @@
##           staging     #388   +/-   ##
========================================
  Coverage    99.92%   99.92%           
========================================
  Files          203      203           
  Lines         2708     2708           
========================================
  Hits          2706     2706           
  Misses           2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@lodewiges lodewiges added this pull request to the merge queue Nov 11, 2024
Merged via the queue into staging with commit 65e944d Nov 11, 2024
5 checks passed
@lodewiges lodewiges deleted the renovate/rubygems-puma-vulnerability branch November 11, 2024 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file prio:critical status:ready to review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant