Add advisory for bip322 - #3150
Open
raphjaph wants to merge 1 commit into
Open
Conversation
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.
Affected crate(s)
Links to upstream issue(s) or PR(s)
https://github.com/rust-bitcoin/bip322
Severity
Critical (9.1/10)
Any application treating successful verification as proof of address ownership
can be compromised. An unauthenticated attacker could impersonate any P2WPKH or
P2SH-P2WPKH wallet to authorize state-changing actions such as withdrawals,
borrowing, or wallet linking. Application-level nonces do not mitigate this,
since the attacker can construct and sign the current challenge message with
their own key.
Checklist
RUSTSEC-0000-0000as the IDdatefield is set to the public disclosure date