Auto-port 4.1: Fix MQTT decoder size check after variable header replay#16838
Merged
Conversation
## Problem The MQTT decoder can reject valid packets after the CVE-2026-44248 fix when several MQTT packets are present in the same cumulation buffer. If the current packet's variable header needs a replay, the decoder compares the total readable bytes in the buffer against `maxBytesInMessage`, so later packets can make the current in-limit packet look too large. ## Root Cause `READ_VARIABLE_HEADER` recorded `buffer.readableBytes()` before decoding the variable header. That value is the cumulation's total readable bytes, not the current MQTT packet's declared remaining length. When `decodeVariableHeader` throws `Signal.REPLAY`, the too-large decision must be based on `bytesRemainingBeforeVariableHeader` for the current packet. ## Fix - Use `bytesRemainingBeforeVariableHeader` when deciding whether to swallow `Signal.REPLAY` and raise `TooLongFrameException`. - Continue replaying when the current packet is within `maxBytesInMessage`, even if the cumulation contains additional bytes for following packets. ## Tests Added | Change Point | Test | |-------------|------| | Variable-header replay uses the current packet size instead of total cumulation bytes for the too-long check | `testPublishMessageIncompleteVariableHeaderDoesNotUseCumulationSizeForTooLongCheck()` verifies an incomplete in-limit PUBLISH variable header with extra cumulated PINGREQ packets does not emit an invalid message | | Oversized current packets still fail during variable-header replay | `testPublishMessageIncompleteVariableHeaderStillFailsWhenCurrentPacketTooLarge()` verifies an incomplete PUBLISH whose own remaining length exceeds `maxBytesInMessage` still emits a `TooLongFrameException` | ## Impact This restores decoding for valid in-limit MQTT packets batched in the same buffer while preserving the CVE fix: packets whose declared remaining length exceeds `maxBytesInMessage` still fail with `TooLongFrameException` even if variable-header decoding requests replay. Fixes #16776 (cherry picked from commit 72df658)
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.
Auto-port of #16787 to 4.1
Cherry-picked commit: 72df658
Problem
The MQTT decoder can reject valid packets after the CVE-2026-44248 fix when several MQTT packets are present in the same cumulation buffer. If the current packet's variable header needs a replay, the decoder compares the total readable bytes in the buffer against
maxBytesInMessage, so later packets can make the current in-limit packet look too large.Root Cause
READ_VARIABLE_HEADERrecordedbuffer.readableBytes()before decoding the variable header. That value is the cumulation's total readable bytes, not the current MQTT packet's declared remaining length. WhendecodeVariableHeaderthrowsSignal.REPLAY, the too-large decision must be based onbytesRemainingBeforeVariableHeaderfor the current packet.Fix
bytesRemainingBeforeVariableHeaderwhen deciding whether to swallowSignal.REPLAYand raiseTooLongFrameException.maxBytesInMessage, even if the cumulation contains additional bytes for following packets.Tests Added
testPublishMessageIncompleteVariableHeaderDoesNotUseCumulationSizeForTooLongCheck()verifies an incomplete in-limit PUBLISH variable header with extra cumulated PINGREQ packets does not emit an invalid messagetestPublishMessageIncompleteVariableHeaderStillFailsWhenCurrentPacketTooLarge()verifies an incomplete PUBLISH whose own remaining length exceedsmaxBytesInMessagestill emits aTooLongFrameExceptionImpact
This restores decoding for valid in-limit MQTT packets batched in the same buffer while preserving the CVE fix: packets whose declared remaining length exceeds
maxBytesInMessagestill fail withTooLongFrameExceptioneven if variable-header decoding requests replay.Fixes #16776