🚨 [security] Update rack 3.2.3 → 3.2.6 (patch)#413
Open
depfu[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚨 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?
✳️ rack (3.2.3 → 3.2.6) · Repo · Changelog
Security Advisories 🚨
🚨 Rack::Request accepts invalid Host characters, enabling host allowlist bypass
🚨 Rack::Sendfile header-based X-Accel-Mapping regex injection enables unauthorized X-Accel-Redirect
🚨 Rack has Content-Length mismatch in Rack::Files error responses
🚨 Rack::Static prefix matching can expose unintended files under the static root
🚨 Rack:: Static header_rules bypass via URL-encoded paths
🚨 Rack's multipart byte range processing allows denial of service via excessive overlapping ranges
🚨 Rack's multipart header parsing allows Denial of Service via escape-heavy quoted parameters
🚨 Rack's greedy multipart boundary parsing can cause parser differentials and WAF bypass.
🚨 Rack's improper unfolding of folded multipart headers preserves CRLF in parsed parameter values
🚨 Rack: Forwarded Header semicolon injection enables Host and Scheme spoofing
🚨 Rack has quadratic complexity in Rack::Utils.select_best_encoding via wildcard Accept-Encoding header
🚨 Rack has a root directory disclosure via unescaped regex interpolation in Rack::Directory
🚨 Rack's multipart parsing without Content-Length header allows unbounded chunked file uploads
🚨 Stored XSS in Rack::Directory via javascript: filenames rendered into anchor href
🚨 Rack has a Directory Traversal via Rack:Directory
Release Notes
3.2.6
3.2.4 (from changelog)
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.
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