FIX: Assertion may be false for untrusted data #4391
Merged
Conversation
This file contains 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
When unpack()-ing untrusted data (e.g. public keys or ciphertexts) it is possible that a debug assertion we made does not hold legitimately. The range check happens later in the deserialiation steps. Co-Authored-By: Fabian Albert <[email protected]>
randombit
approved these changes
Oct 17, 2024
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.
When unpack()-ing untrusted data (e.g. public keys or ciphertexts) it is possible that a debug assertion we made does not hold legitimately. The range check happens later in the deserialization steps.
Note that this only really becomes a problem when configuring
--with-debug-asserts --unsafe-terminate-on-asserts(as we do for sanitizer builds)This is a fix for: #4375 (comment).