stake.link

Summary

Function call conflict while calling from a proxy.

Vulnerability Details

There are a function named onTokenTransfer() is present in both of this contract SDLPoolPrimary and WrappedTokenBridge. Both of these function selector are same:

Impact

In a system where two different contracts, not connected to each other, have methods with the same function selector, it could lead to unexpected behavior when these methods are invoked through a proxy contract. This is because the proxy contract will not be aware of which specific contract's function to execute when a function with a clashing selector is called.

Tools Used

Manual analysis.

Recommendations

Change the function name.