fix(ctap2): preserve raw authenticatorData bytes#249
Merged
Conversation
The authenticator signs over the exact authData bytes, including the extensions block. Rebuilding authData from the parsed struct could drop unmodeled extensions or reorder keys, breaking the relying party's signature verification. Keep the device bytes and return them unchanged. Platform-synthesized U2F authData still rebuilds from the fields.
89bb140 to
97eaaf2
Compare
This was referenced Jun 7, 2026
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.
The client rebuilt the authenticator data from a parsed structure instead of keeping the exact bytes the authenticator produced. An authenticator signature covers those exact bytes, so re-encoding could drop extension entries the client did not model or reorder map keys, which would make a relying party reject an otherwise-valid signature. This was confirmed against a real device response carrying an extension the client did not model.
This keeps the authenticator data verbatim and returns it unchanged. Platform-synthesized data is still built from fields.
Includes a regression test confirming the bytes round-trip unchanged, including an unmodeled extension.