Core Contracts

Regnum Aurum Acquisition Corp
HardhatReal World AssetsNFT
77,280 USDC
View results
Submission Details
Severity: low
Valid

Mismatch between `TimelockController` documentation and code

Summary

The TimelockController documentation specifies that every emergency action that needs to be executed needs to have an EMERGENCY_DELAY so that all users can take proper measures. However, the contract does not enforce such a delay, and all scheduled emergency actions can be executed immediately.

Vulnerability Details

As per the documentation:

Emergency actions have 1-day delay

This delay is evident from the code as well:

/// @notice Delay for emergency actions (1 day)
uint256 public constant EMERGENCY_DELAY = 1 days;

However, executeEmergencyAction does not enforce it, and actions can be executed immediately.

Impact

Users can't react to emergency actions, due to missing delay, which may force them to participate in the protocol under unfavorable conditions.

Tools Used

Manual review

Recommendations

Enforce a 1-day delay to all emergency actions.

Updates

Lead Judging Commences

inallhonesty Lead Judge 7 months ago
Submission Judgement Published
Validated
Assigned finding tags:

TimelockController emergency actions bypass timelock by not enforcing EMERGENCY_DELAY, allowing immediate execution

inallhonesty Lead Judge 7 months ago
Submission Judgement Published
Validated
Assigned finding tags:

TimelockController emergency actions bypass timelock by not enforcing EMERGENCY_DELAY, allowing immediate execution

Support

FAQs

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

Give us feedback!