mediumLogic errorEVM-Solidity
Perennial V2 Update #3: TriggerOrder.notionalValue() Using the wrong latestPositionLocal to calculate the value causes the user to overpay fees
- Payout
- $0
- Protocol
- Perennial V2 Update #3
- Disclosed
- Sep 13, 2024
- Source
- sherlock
Perennial V2's TriggerOrder type computes the interface fee charged for closing a position from a different position snapshot than the one the market actually closes. When delta equals MAGIC_VALUE_CLOSE_POSITION, TriggerOrder._position() reads the latest commi …
Similar reports
- No close matches yet.
References
This report is already public and closed. Coin Buggie never publishes active or unpatched vulnerability data.