Fix WebSocket UTF-8 validation crash#159
Closed
whatyouhide wants to merge 1 commit into
Closed
Conversation
Invalid UTF-8 text payloads could crash continuation states in the WebSocket UTF-8 decoder when an ASCII byte appeared where a continuation byte was expected. Return the UTF-8 error state instead so text, close and fragmented payloads fail as badencoding.
Member
|
I'll merge on Monday, thank you. |
Member
|
Merged, thanks! |
Contributor
Author
|
Thank you! |
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.
Clsoes #158.
Invalid UTF-8 text payloads could crash continuation states in the WebSocket UTF-8 decoder when an ASCII byte appeared where a continuation byte was expected.
Return the UTF-8 error state instead so text, close and fragmented payloads fail as badencoding.