Repository navigation
Cover frame header field boundaries and invalid sizes - #173
Open
ryanduguid wants to merge 1 commit into
Open
ryanduguid wants to merge 1 commit into
ryanduguid wants to merge 1 commit into
Conversation
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.
Summary
Add 35 frame-header cases covering 24-bit lengths, nonzero stream IDs with the reserved bit set, unknown-frame flags and error metadata, and buffers shorter or longer than nine bytes.
Evidence
The fault injections and verification helpers are outside the PR.
Merge danger
Door: two-way. Blast radius: tests.
Only
tests/test_frame_header.pyis added.Unverified
macOS, other Windows versions, Windows documentation/packaging, hosted CI, scanner parser coverage and maintainer acceptance. Packaging succeeds with warnings about unchanged license metadata and empty exclusion patterns.