Core Contracts
Regnum Aurum Acquisition Corp
HardhatReal World AssetsNFT
77,280 USDC
View results
Previous Next
Submission Details
Severity: medium
Invalid

`BaseGauge::MAX_SLIPPAGE` protection defined but never used

kiteweb3

Summary

The BaseGauge contract defines a MAX_SLIPPAGE constant of 100 (1%) that is intended to protect against large changes in weights. However, while this constant is defined and documented (Ref. BaseGauge.md Usage Notes: Slippage protection on weight updates), no actual implementation exists to enforce this slippage protection. The contract allows arbitrary changes to weights without any bounds checking against the defined maximum slippage value.

Vulnerability Details

/// @notice Maximum allowed slippage (1%)
@> uint256 public constant MAX_SLIPPAGE = 100;

Impact

The lack of slippage protection means that the weight updates can occur with unlimited percentage changes, leaving the system to allow any sudden large changes in reward distribution. This can lead the system to economic lost.

Tools Used

Manual review

Recommendations

Implement slippage protection when the weight is updated.

Updates

Lead Judging Commences

inallhonesty Lead Judge 7 months ago
Submission Judgement Published
Invalidated
Reason: Non-acceptable severity
inallhonesty Lead Judge 7 months ago
Submission Judgement Published
Invalidated
Reason: Non-acceptable severity

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.

Give us feedback!