Submitted by jonah1005, also found by defsec
createPool is a permissionless transaction.
Assume a new popular coin that the DAO decides to add to the protocol.
The attacker can create the pool and set it to be extremely cheap. (By depositing 1 wei coin and 10^18 wei Vader.) The attacker can mint a lot of synth by providing another 10^18 wei Vader.
Theres no way to revoke the pool. The coin pool would be invalid since the attacker can drain all the lp in the pool.
I consider this is a high-risk issue.
None
Restrict users from minting synth from a new and illiquid pool.
Some thoughts about the fix:
The pool can remain permissionless and safe.
SamSteinGG (Vader) disputed:
alcueca (judge) commented:
SamSteinGG (Vader) commented:
