NestedFactory: Ensure zero msg.value if transferring from user and inputToken is not ETH #136
Labels
2 (Med Risk)
Assets not at direct risk, but function/availability of the protocol could be impacted or leak value
bug
Something isn't working
sponsor confirmed
Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")
Handle
GreyArt
Vulnerability details
Impact
A user that mistakenly calls either
create()
oraddToken()
with WETH (or another ERC20) as the input token, but includes native ETH with the function call will have his native ETH permanently locked in the contract.Recommended Mitigation Steps
It is best to ensure that
msg.value = 0
in_transferInputTokens()
for the scenario mentioned above.The text was updated successfully, but these errors were encountered: