EbmlMaster: fix invalid reads#352
Merged
Merged
Conversation
We found an upper element and there is not data to read after the current element within its parent. That upper element is misplaced and should be discarded. The last element is truncated and doesn't contain the rest of its data.
When an element from an upper level is found we go up the caller chain, passing the found element but it was not actually used (added to a list or freed). This patch allows setting that element as the ElementLevelA found in the loop. We skip the call the inDataStream.FindNextElement() to find it. The new MaxSizeToRead is the size to read in the next inDataStream.FindNextElement() call. The old MaxSizeToRead <= 0 code seems bogus as it would exit the loop to find elements for that EbmlMaster even though there might still be elements to read.
…arent It could be a file with missing data in the middle. And we shouldn't use a MaxSizeToRead that would be negative. Missing backport to master Reported-by: Benjamin Ali (glitchfox) <glitchfox@benjaminali.com>
retokromer
approved these changes
Jul 23, 2026
mbunkus
approved these changes
Jul 24, 2026
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.
missing "backports" of #338, #341, and #322
Reported-by: Benjamin Ali (glitchfox) glitchfox@benjaminali.com