Reject zero-length AEAD authentication tags (GH #1364) - #1365
Open
Coralesoft wants to merge 1 commit into
Open
Conversation
GCM, EAX, CCM, ChaCha20-Poly1305, and XChaCha20-Poly1305 accepted zero-length authentication tags through EncryptAndAuthenticate, DecryptAndVerify, and the authenticated filters. Verification with a zero-length tag could report tampered ciphertext as authentic. Reject a zero tag size in AuthenticatedSymmetricCipherBase::TruncatedFinal, which all five algorithms and both filter paths reach during finalisation.
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.
Fixes #1364.
GCM, EAX, CCM, ChaCha20-Poly1305, and XChaCha20-Poly1305 accepted zero-length authentication tags through the one-shot APIs and authenticated filters.
EncryptAndAuthenticateproduced no tag, andDecryptAndVerifycould report tampered ciphertext as authentic. Reject a zero tag size inAuthenticatedSymmetricCipherBase::TruncatedFinal, which every affected path reaches during finalisation.The one-shot APIs process the message before finalisation, so output buffers may already contain data when the exception is thrown. Callers must discard that output.
The reporter's reproducer finds both affected cases before this change and none after it. Valid-tag controls still pass.