[Info] ChainId is not used in signatures, which could lead to replay attacks if WinnablesTicketManager
Summary
ChainId is not used in signatures, which could lead to replay attacks in WinnablesTicketManager when buying tickets.
Vulnerability Detail
When buying a ticket, the offline generated signature is checked and verified in order to let users buy the tickets they wanted to. But in the signature verification chainId is not included which can lead to replay attacks if the WinnablesTicketManager is deployed on another network and the raffleId on one network matches another raffleId on the other network.
Impact
This is low/info as currently the WinnablesTicketManager is supposed to be deploed only on Avalanche and furthermore, there is a blockNumber included before which the tickets can be bought, which further limits the attack.
Rich Marigold Swan
Low/Info
[Info] ChainId is not used in signatures, which could lead to replay attacks if WinnablesTicketManager
Summary
ChainId is not used in signatures, which could lead to replay attacks in WinnablesTicketManager when buying tickets.
Vulnerability Detail
When buying a ticket, the offline generated signature is checked and verified in order to let users buy the tickets they wanted to. But in the signature verification chainId is not included which can lead to replay attacks if the WinnablesTicketManager is deployed on another network and the raffleId on one network matches another raffleId on the other network.
Impact
This is low/info as currently the WinnablesTicketManager is supposed to be deploed only on Avalanche and furthermore, there is a blockNumber included before which the tickets can be bought, which further limits the attack.
Code Snippet
Tool used
Manual Review
Recommendation
Add chainId to the offline signature and include it in the verification of the signature also: