Cap ReadFrame allocations from peer-declared length - #226
Open
AshSgDe29071999 wants to merge 1 commit into
Open
AshSgDe29071999 wants to merge 1 commit into
AshSgDe29071999 wants to merge 1 commit into
Conversation
ReadFrame allocated make([]byte, Header.Length) with no limit, so a post-handshake peer could declare a huge payload and OOM the process. Honor MaxFramePayloadSize (default 32MiB). See gobwas#223
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.
ReadFrameallocatedmake([]byte, Header.Length)with no limit, so a post-handshake peer could declare a huge payload and OOM the process.Honor
MaxFramePayloadSize(default 32MiB). Set it to 0 to restore the old unlimited behavior.wsutil.ReadMessageuses the same cap.Fixes #223
Test
go test . -run TestReadFrameRejectsOversizedPayload -count=1