Lucene search
+L

4 matches found

Code423n4
Code423n4
added 2022/02/06 12:00 a.m.9 views

Owner can steal input tokens

Lines of code Vulnerability details Impact Owner is in full control over the saleRecipient address. When a buy transaction enters the mempool, an owner can frontrun the buy with a transaction that calls setTokenOutPrice and sets the price to a very high value, effectively making bought tokens clo...

6.8AI score
SaveExploits0
Code423n4
Code423n4
added 2022/02/06 12:00 a.m.12 views

Possible rug #3

Lines of code Vulnerability details Impact Tokens can be consumed by the contract and sent to the saleRecipient address without any guarantee that sale tokens will ever be deposited in the sale contract. The sold tokens are only required in the finalize function, which clearly does not provide an...

6.8AI score
SaveExploits0
Code423n4
Code423n4
added 2022/02/06 12:00 a.m.14 views

[WP-H3] saleRecipient can rug buyers

Lines of code Vulnerability details In TokenSaleUpgradeable.solbuy, tokenIn will be transferred from the buyer directly to the saleRecipient without requiring/locking/releasing the correspoining amount of tokenOut. This allows the saleRecipient to rug the users simply by not transferring tokenOut...

6.7AI score
SaveExploits0
Code423n4
Code423n4
added 2022/02/06 12:00 a.m.11 views

TokenIn can be swept if saleRecipient == tokenSale

Lines of code Vulnerability details The initialize and setSaleRecipient function allows setting the saleRecipient to the contract itself, which means the tokenIn will remain in the contract. It can then be transferred out by calling sweep. This condition described in sweep does not hold anymore...

6.8AI score
SaveExploits0
Rows per page
Query Builder