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] #546

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2024

This PR contains the following updates:

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

GitHub Vulnerability Alerts

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 Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 dependencies Pull requests that update a dependency file renovate labels Jan 8, 2024
@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 Jul 13, 2024
@renovate renovate bot closed this Jul 13, 2024
@renovate renovate bot deleted the renovate/rubygems-puma-vulnerability branch July 13, 2024 14:44
@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] Jul 14, 2024
@renovate renovate bot reopened this Jul 14, 2024
@renovate renovate bot restored the renovate/rubygems-puma-vulnerability branch July 14, 2024 08:32
@renovate renovate bot force-pushed the renovate/rubygems-puma-vulnerability branch from babfd64 to 53889de Compare July 14, 2024 08:32
@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 53889de to 87ce0b0 Compare September 20, 2024 16:55
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 renovate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants