If in future implementations, the bridge allows opting for tokens with the same address, the signature provided by the operator can be reused across different chains to drain funds.
Currently, the message signed by the operator does not distinguish between chains. However, when tokens with different addresses are created using create(), there is currently no way to maliciously reuse the signature in others chains. Nevertheless, if this were to change in the future, with the current verifications, a malicious user could reuse the same signature across different chains to drain funds.
Potential loss of all funds.
Foundry
Add a distinctive feature, including block.chainid in the message to be hashed.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.