-
Notifications
You must be signed in to change notification settings - Fork 10
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
🔒 M-01 - Prevent Replay Attacks by Enforcing Signature Malleability Check #119
Conversation
🤖 Slither Analysis Report 🔎Slither report
# Slither report
_This comment was automatically generated by the GitHub Actions workflow._
THIS CHECKLIST IS NOT COMPLETE. Use
constable-statesImpact: Optimization
|
Hang on.. in any case we should probably use oz ECDSA library directly instead of making s checks in our code. |
It uses the same logic as in the OZ ECDSA library, the signature with the lower 's' value is considered valid. |
I agree with the code size concerns, that's something that will need to fix after the remediations. But Libraries works in a way that it will extend the code size only for the used functions, so it will not add the whole library codesize |
Yeah you aren't inheriting really so it's not a codesize thing.. |
M-01. Potential Replay Attack Vulnerability in Signature Verification Logic
s
value.s
value is greater than0x7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF5D576E7357A4501DDFE92F46681B20A0
.