Submitted by cmichel, also found by gzeon
The TurboSafe.slurp function fetches the current fee from the clerk().
This fee can be changed.
The slurp transaction can be frontrun with a fee increase (specifically targeted for the vault or the asset) by the clerk and steal the vault yield that should go to the user.
Maybe the user would not want to slurp at the new fee rate and would rather wait as they expect the fees to decrease again in the future.
Or they would rather create a new vault if the default fees are lower.
Right now theres no good protection against this as the master can call slurp at any time.
(They could even increase the fees to 100%, slurp, reset the fees.)
This mechanic would need to be addressed first if mitigation and better user protection are desired.
Joeysantoro (Tribe Turbo) disputed and commented:
Alex the Entreprenerd (judge) commented:
