Repository navigation
Conversation
Collaborator
|
Review requested:
|
legendecas
requested changes
Jul 21, 2026
cola119
approved these changes
Jul 26, 2026
Contributor
Author
|
gentle ping |
This comment was marked as outdated.
This comment was marked as outdated.
legendecas
approved these changes
Aug 28, 2026
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Collaborator
This comment was marked as outdated.
This comment was marked as outdated.
Member
|
@Nashit-h please fix the linter issues, rebase and force push. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #64618 +/- ##
==========================================
- Coverage 90.69% 90.69% -0.01%
==========================================
Files 797 797
Lines 278787 278788 +1
Branches 53607 53609 +2
==========================================
- Hits 252858 252836 -22
- Misses 16292 16300 +8
- Partials 9637 9652 +15
🚀 New features to boost your workflow:
|
cola119
approved these changes
Sep 12, 2026
cola119
left a comment
Member
There was a problem hiding this comment.
lgtm when the formatter error is fixed
Signed-off-by: nashit hayyat <nashit@bugqore.com>
Nashit-h
force-pushed
the
ws-frame-bounds-check
branch
from
October 31, 2026 05:49
1958e12 to
c0ef71e
Compare
Contributor
Author
|
Done. Rebased on main, squashed the two commits into one, and applied the clang-format reflow on the FRAME_BODY initializer that format-cpp was asking for. No code changes beyond that line wrap. |
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.
decode_frame_hybi17 checks the announced payload length against buffer.size(), but the payload is read from it + kMaskingKeyWidthInBytes, after the iterator has already walked past the two byte header and the extended length field. A client that sends only the two header bytes of a masked frame, 0x81 0xFD, underflows buffer.size() - kMaskingKeyWidthInBytes to SIZE_MAX, passes the check, and the unmasking loop reads 125 bytes past a two byte vector; the bytes it picks up go to OnWsFrame and back out to the peer. Measuring against what is left after the header fixes both that underflow and the header bytes the old check never accounted for.