🚨 [security] Update rack 2.2.8 → 2.2.23 (patch)#386
Open
depfu[bot] wants to merge 1 commit intomasterfrom
Open
🚨 [security] Update rack 2.2.8 → 2.2.23 (patch)#386depfu[bot] wants to merge 1 commit intomasterfrom
depfu[bot] wants to merge 1 commit intomasterfrom
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?
Security Advisories 🚨
🚨 Rack::Static prefix matching can expose unintended files under the static root
🚨 Rack has Content-Length mismatch in Rack::Files error responses
🚨 Rack::Sendfile header-based X-Accel-Mapping regex injection enables unauthorized X-Accel-Redirect
🚨 Rack's multipart parsing without Content-Length header allows unbounded chunked file uploads
🚨 Rack has a root directory disclosure via unescaped regex interpolation in Rack::Directory
🚨 Rack has quadratic complexity in Rack::Utils.select_best_encoding via wildcard Accept-Encoding header
🚨 Rack's greedy multipart boundary parsing can cause parser differentials and WAF bypass.
🚨 Rack's multipart byte range processing allows denial of service via excessive overlapping ranges
🚨 Rack:: Static header_rules bypass via URL-encoded paths
🚨 Stored XSS in Rack::Directory via javascript: filenames rendered into anchor href
🚨 Rack has a Directory Traversal via Rack:Directory
🚨 Rack has a Possible Information Disclosure Vulnerability
🚨 Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing
🚨 Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion)
🚨 Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion)
🚨 Rack: Multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion)
🚨 Rack has an unsafe default in Rack::QueryParser allows params_limit bypass via semicolon-separated parameters
🚨 Rack has an Unbounded-Parameter DoS in Rack::QueryParser
🚨 Rack session gets restored after deletion
🚨 Local File Inclusion in Rack::Static
🚨 Escape Sequence Injection vulnerability in Rack lead to Possible Log Injection
🚨 Possible Log Injection in Rack::CommonLogger
🚨 Rack vulnerable to ReDoS in content type parsing (2nd degree polynomial)
🚨 Rack Header Parsing leads to Possible Denial of Service Vulnerability
🚨 Rack has possible DoS Vulnerability with Range Header
Release Notes
2.2.23 (from changelog)
2.2.21 (from changelog)
2.2.19 (from changelog)
2.2.16 (from changelog)
2.2.15 (from changelog)
2.2.14 (from changelog)
2.2.13 (from changelog)
2.2.12 (from changelog)
2.2.10 (from changelog)
2.2.8.1
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.
🆕 mini_portile2 (added, 2.8.9)
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