fix: possible leak on base64 decode failure#338
Merged
Conversation
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.
decoder.decode can fail on malformed base64 input after text has already been allocated, this adds an errdefer so the temporary allocation is released if decode fails before ownership transfer.
for repro I used a simple test to confirm the leak, I didn't add this to the pr so as not to bloat the test set:
test "parse: osc52 paste with malformed base64 does not leak" {
const alloc = testing.allocator_instance.allocator();
// "!!!!" is not valid base64; decode() will return error.InvalidCharacter
const input = "\x1b]52;c;!!!!\x1b\";
var parser: Parser = .{};
try testing.expectError(error.InvalidCharacter, parser.parse(input, alloc));
}