Repository navigation
Update dependency rack to v3.2.9 - #82
Merged
Merged
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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.
This PR contains the following updates:
'3.2.8'→'3.2.9'Release Notes
rack/rack (rack)
v3.2.9Compare Source
Security
charset, allowing denial of service via CPU exhaustion.Rack::Directorylisted directories outside the root when..followed a symbolic link.Rack::Multipart::Parserdid not unfold a foldedContent-IDheader, preserving CRLF in the parsed parameter name.Rack::QueryParserseparator pattern allocated about 48 bytes per space after&, and nested parameter name splitting about 48 bytes per bracket, allowing denial of service via memory amplification.DEFAULT_SEPand theCOMMON_SEPentries for∧are now Strings rather than Regexps.Changed
Content-Typeheader is now parsed according to RFC 9110. An unquotedboundarycontaining characters outside the token grammar (such as=,/,:,?, parentheses, or spaces), or parameters not separated by;, now raiseRack::Multipart::Errorinstead of being accepted. Quoted boundaries are unaffected. (@jeremyevans, @tenderlove)Fixed
Rack::Multipartno longer raisesTypeErrorfor a part withcharset=internalwhen no default internal encoding is set; the part is treated as binary.Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.