security: bound livekit audio decode by frame data length - #1035
Open
eordano wants to merge 1 commit into
Open
Conversation
The decode loops indexed `frame.data` by the wire-declared samples_per_channel, so a peer could set it past the buffer and panic. Cap the loop at data.len(). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
The LiveKit audio path indexes a decoded frame using a length taken from the frame header rather than the delivered data, so a peer-supplied frame whose header overstates its payload panics the decode.
Bound the decode by the actual data length.
+4/-2. Reachable from any peer publishing audio. Marginal for a headless server, which has no audio sink and does not subscribe, so this is really client hardening — included because it is peer-triggered and cheap.