reject control characters in bearer token in BearerScheme - #863
Merged
Conversation
Contributor
Author
|
TY! |
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
2 participants
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.
BearerScheme writes the token straight into the Authorization header, and unlike BasicScheme it never checks the credential for control characters. A bearer token carrying CR/LF is neutralised by the HTTP/1.1 line formatter, which replaces those bytes with spaces, but the HTTP/2 request converter passes header values through unchanged, so over h2 such a token can inject extra header material into the request. This applies the same control-character guard BasicScheme already uses, rejecting the token before the header is built.