Decent Smoke Owl
High
There are not checks in OracleLess
contract to verify that tokens used are supported.
No checks when creating orders that tokens are supported.
N/A
N/A
Providing two examples:
Protocol is not designed to support FoT tokens and using such tokens would brick the tokens accounting.
Creating orders with custom malicious tokens can prevent admin of canceling such order as when canceling an order it is needed to transfer the tokenIn to the recipient. Malicious tokens can for example blackist the OracleLess
contract and the function will revert. Not being able to cancel order would lead to indefinitely grow of pendingOrderIds
array leading to DoS because of block gas limit.
Unexpected behaviour - wrong accounting, DoS.
No response
Add whitelisting mechanism.