Fluid Protocol
Reports by Severity
Critical
#37671 [SC-Critical] CRITICAL-02 / The contract could be permanently locked due to not reseting the boolen lock
#37323 [SC-Critical] Permanent dead Lock in internal_redeem_collateral_from_trove
#37452 [SC-Critical] `trove-manager-contract.redeem_collateral_from_trove` can be locked forever
#37624 [SC-Critical] Lock Issue Bricks The Redeem Functionality
Low
#37668 [SC-Low] Incorrect Scale Factor value leads to early scale change
#37650 [SC-Low] Redeem Functionality Partially Failing
#37354 [SC-Low] Single below MCR trove temporarily blocks redemptions
#37283 [SC-Low] Improper Trove Validation Check Allows Low-Cost Griefing Attack to Block Protocol Redemptions
#37192 [SC-Low] Trove that under MCR might be redeemed.
#37409 [SC-Low] Can not redeem when all `current_cr` less than `MCR`.
#37607 [SC-Low] Bricking Redeem Function
Insight
#36922 [SC-Insight] the function claim_collateral in borrowOperation have read only attribute while the invoked claim_collateral function have write attribute, this lead to compiler-time error
#37139 [SC-Insight] INSIGHT: Inefficient Use of Storage Reentrancy Locks
#37056 [SC-Insight] `require_at_least_min_net_debt` did not emit correct error message
#37202 [SC-Insight] some checks can be removed since its not required(best practice report, not an issue)
#37343 [SC-Insight] Inaccurate Check Leading to Debt Miscalculation
#37382 [SC-Insight] Inconsistent Collateral Ratio Checks in Stability Pool Withdrawals Lead to Fund-Locking DoS
#37425 [SC-Insight] redeem_collateral does not redeem collateral from riskiest trove but wrongly redeem lowest healthy troves with lowest collateral Ratio
#37595 [SC-Insight] `require_caller_is_bo_or_tm_or_sp_or_pm` did not emit correct message
Reports by Type
Smart Contract
#37668 [SC-Low] Incorrect Scale Factor value leads to early scale change
#37650 [SC-Low] Redeem Functionality Partially Failing
#37276 [SC-Medium] Redstone's price feed is used incorrectly.
#36922 [SC-Insight] the function claim_collateral in borrowOperation have read only attribute while the invoked claim_collateral function have write attribute, this lead to compiler-time error
#37139 [SC-Insight] INSIGHT: Inefficient Use of Storage Reentrancy Locks
#37354 [SC-Low] Single below MCR trove temporarily blocks redemptions
#37671 [SC-Critical] CRITICAL-02 / The contract could be permanently locked due to not reseting the boolen lock
#37056 [SC-Insight] `require_at_least_min_net_debt` did not emit correct error message
#37202 [SC-Insight] some checks can be removed since its not required(best practice report, not an issue)
#37283 [SC-Low] Improper Trove Validation Check Allows Low-Cost Griefing Attack to Block Protocol Redemptions
#37323 [SC-Critical] Permanent dead Lock in internal_redeem_collateral_from_trove
#37343 [SC-Insight] Inaccurate Check Leading to Debt Miscalculation
#37382 [SC-Insight] Inconsistent Collateral Ratio Checks in Stability Pool Withdrawals Lead to Fund-Locking DoS
#37192 [SC-Low] Trove that under MCR might be redeemed.
#37425 [SC-Insight] redeem_collateral does not redeem collateral from riskiest trove but wrongly redeem lowest healthy troves with lowest collateral Ratio
#37409 [SC-Low] Can not redeem when all `current_cr` less than `MCR`.
#37452 [SC-Critical] `trove-manager-contract.redeem_collateral_from_trove` can be locked forever
#37595 [SC-Insight] `require_caller_is_bo_or_tm_or_sp_or_pm` did not emit correct message
#37607 [SC-Low] Bricking Redeem Function
#37624 [SC-Critical] Lock Issue Bricks The Redeem Functionality
Was this helpful?