Fix ByteBuf Memory Leaks in DecryptJob and GCMCryptoService #3170
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.
Summary
DecryptJob.closeJob() does not release encryptedBlobContent when called.
DecryptJob owns encryptedBlobContent after construction and must release it in all exit paths.
GCMCryptoService.decrypt() exception handler releass caller's buffer instead of service's buffer.
Input toDecrypt ownership is retained by the caller. Service must not touch it Output decryptedContent is owned by service until it returns. Service must release on error.
Fix 1: DecryptJob.closeJob() release owned buffer
Fix 2: GCMCryptoService.decrypt() released correct buffer
Testing Done
testDecryptJobCloseBeforeRunReleasesBuffer()
testDecryptJobCloseIdempotent()
testDecryptJobNormalExecutionNoLeak()
testDecryptWithCorruptedCiphertextOwnership()
testDecryptWithWrongKeyOwnership()
testSuccessfulDecryptOwnership()