ERC20 transfer()
may return nothing
#332
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
duplicate
This issue or pull request already exists
Lines of code
https://github.com/code-423n4/2022-10-holograph/blob/f8c2eae866280a1acfdc8a8352401ed031be1373/contracts/enforcer/PA1D.sol#L416
https://github.com/code-423n4/2022-10-holograph/blob/f8c2eae866280a1acfdc8a8352401ed031be1373/contracts/enforcer/PA1D.sol#L439
Vulnerability details
Impact
Some tokens do not comply with the standard. The
transfer()
function may have no return value, such as USDT. In such cases, the payout functions will revert and users fund may be locked.Proof of Concept
Tools Used
Manual analysis.
Recommended Mitigation Steps
Use openzeppelin wrapper for ERC20 transfer.
The text was updated successfully, but these errors were encountered: