-
Notifications
You must be signed in to change notification settings - Fork 3
F-8045 - Reject duplicate SCEP signed attributes #20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
yosuke-wolfssl
wants to merge
1
commit into
wolfSSL:main
Choose a base branch
from
yosuke-wolfssl:fix/f_8045
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
seenbitmask catches the same OID appearing in twoAttributeSEQUENCEs, but not twoAttributeValues inside one attribute's SET.wc_PKCS7_ParseAttribscreates onePKCS7DecodedAttribper SEQUENCE and copies the SET's content intovaluewithvalueSzcovering the whole SET - it never iterates the values inside. SotransactionID ::= SET { PrintableString "A", PrintableString "B" }yields one list node, one bit, and no collision. The unwrap below then reads the first value and thevoff + vlen > a->valueSzcheck lets the trailing bytes through, so the message is accepted with*out_transaction_id == "A".Not a leak, and the first-value pick is pre-existing rather than a regression - but it does mean a peer can still hand
handle_pki_opandscep_finishtwo values for one attribute and have us act on one of them without complaint. RFC 8894 defines each of these as single-valued, so by the same argument the rest of this change makes, I'd require the value to fill the SET:That equality holds in both shapes the code handles, and it reuses the reject path you already added, so there is no extra rollback to write. Covering it in
test_duplicate_signed_attribneeds a hand-encoded SignedData - wolfSSL'sEncodeAttributesemits one SET perPKCS7Attriband cannot produce the input.