withdrawETH() in Basket uses transfer() to send ETH, CALL() SHOULD BE USED INSTEAD OF TRANSFER() ON AN ADDRESS PAYABLE

[code423n4]

Lines of code

https://github.com/code-423n4/2022-06-nibbl/blob/8c3dbd6adf350f35c58b31723d42117765644110/contracts/Basket.sol#L77-L82

Vulnerability details

Impact

This is a classic Code4rena issue:

https://github.com/code-423n4/2021-04-meebits-findings/issues/2 https://github.com/code-423n4/2021-10-tally-findings/issues/20 https://github.com/code-423n4/2022-01-openleverage-findings/issues/75

Proof of Concept

The use of the deprecated transfer() function for an address will inevitably make the transaction fail when:

The claimer smart contract does not implement a payable function. The claimer smart contract does implement a payable fallback which uses more than 2300 gas unit. The claimer smart contract implements a payable fallback function that needs less than 2300 gas units but is called through proxy, raising the call’s gas usage above 2300. Additionally, using higher than 2300 gas might be mandatory for some multisig wallets.

Tools Used

VIM

Recommended Mitigation Steps

I recommend using call() instead of transfer().

[mundhrakeshav]

18

[HardlyDifficult]

Agree that using .transfer is now discouraged. I think a difference here as compared to other contests is that the _to address is simply an input to this function call -- so if it reverts they could try again with a EOA and then transfer manually to the contract. Lowering risk and converting this into a QA report for the warden.

[HardlyDifficult]

Merging with https://github.com/code-423n4/2022-06-nibbl-findings/issues/161

[HardlyDifficult]

Merging with https://github.com/code-423n4/2022-06-nibbl-findings/issues/163 & https://github.com/code-423n4/2022-06-nibbl-findings/issues/169