fix(HTTP): strip CRLF from DownloadResponse filename to prevent header injection - #10533
Open
gr8man wants to merge 1 commit into
Open
fix(HTTP): strip CRLF from DownloadResponse filename to prevent header injection#10533gr8man wants to merge 1 commit into
gr8man wants to merge 1 commit into
Conversation
…r injection Sanitize carriage return and newline characters from filename in DownloadResponse to prevent HTTP response splitting and invalid header values per RFC 7230.
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
1 participant
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.
Description
In
DownloadResponse, filenames with carriage return (\r) or newline (\n) characters could cause RFC 7230 header validation errors or lead to HTTP header injection / response splitting.This PR strips
\rand\ncharacters from the filename when setting it onDownloadResponse.Checklist: