fix: prevent stack exhaustion in packet parser from zero-length uintv frames - #10
Merged
MixaMega merged 7 commits intoMay 17, 2026
Merged
Conversation
…on players that send zero-length frames
… with iterator functions
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.
Fixed a DoS vulnerability that allowed any unauthenticated client to crash the server by exhausting the call stack.
The
readMessagesfunction in the packet handler used recursion when processing variable-length integer (uintv) frames. By sending a large number of0x01bytes (which encode zero-length frames), an attacker could trigger deep recursive calls without making meaningful progress, eventually causing aMaximum call stack size exceedederror.This attack required only a raw TCP connection, no authentication or valid packets needed, as
uintvparsing happens before any of those.Impact
What i did
readMessageswith an iterator (while loop)readUIntVthrow on zero-length frames and madeparsePacketcatch those exceptions applying a sanction to the malicious connectionPoC