ASN.1 parsing: check for badly encode negative INTEGER#7332
Merged
JacobBarthelmeh merged 1 commit intowolfSSL:masterfrom Mar 15, 2024
Merged
ASN.1 parsing: check for badly encode negative INTEGER#7332JacobBarthelmeh merged 1 commit intowolfSSL:masterfrom
JacobBarthelmeh merged 1 commit intowolfSSL:masterfrom
Conversation
When encoding a negative number, when the first byte is 0xff then the next byte can't have top bit set.
dgarske
approved these changes
Mar 14, 2024
JacobBarthelmeh
approved these changes
Mar 15, 2024
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
4 participants
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.
Description
When encoding a negative number, when the first byte is 0xff then the next byte can't have top bit set.
Fixes zd#17627
Testing
Compiled - checking with reporter.
Checklist