Open codehawks-bot opened 1 year ago
According to time elapsed after deployment of the proxy some malicious user can send bad tokens to proxy address after it received the usdc might lead the proxy locked down .This way all the funds the proxy has will be blocked by USDC main contract .I wasnt meant of winners addresses.
If the protocol itself is blocklisted, you can't do anything. Also, you can't send tokens to a blocklisted address. So this recommendation wouldn't help either.
Technically, this submission is invalid, but we lumped your blocklisted finding in because blocklisted addresses are an issue, just not the proxy. The root cause is there, but the attack vector is wrong.
Leaving as such.
Proxy address can be blocklisted by Token like USDC
Severity
High Risk
Relevant GitHub Links
https://github.com/Cyfrin/2023-08-sparkn/blob/0f139b2dc53905700dd29a01451b330f829653e9/src/ProxyFactory.sol#L76C1-L90C6
Summary
Proxy address can be blocklisted by Token like USDC
Vulnerability Details
Proxy address can be predicted before cause of salt is emitted across chain.Using this parameter to know the address ahead and can be forced to blocklist by malicious actors sending dangerous tokens
Impact
Proxy contract wont be able to transfer its tokens to winners.
Here's simple mockUSDC contract i made
Tools Used
Foundry Test suite
Recommendations
Before sending usdc token check the proxy address if its address blocklisted .