Submission Details
Severity:
Consider Using `Ownable2Step` rather than `Ownable`
Summary
To enhance the security and prevent inadvertent ownership transfers, it's advisable to use Ownable2Step or Ownable2StepUpgradeable.
Vulnerability Details
Contracts necessitate an active confirmation from the recipient before the ownership transfer is finalized.
This mechanism serves as a safeguard against scenarios where, for instance, a typo in the address could lead to unintentional ownership changes.
File: contracts/SmartVaultManagerV5.sol
4: import "@openzeppelin/contracts-upgradeable/access/OwnableUpgradeable.sol";
16: contract SmartVaultManagerV5 is ISmartVaultManager, ISmartVaultManagerV2, Initializable, ERC721Upgradeable, OwnableUpgradeable {
File: contracts/LiquidationPoolManager.sol
5: import "@openzeppelin/contracts/access/Ownable.sol";
11: contract LiquidationPoolManager is Ownable {
Tools Used
VSCode
Recommendations
Use Ownable2Step or Ownable2StepUpgradeable
Updates
Lead Judging Commences
hrishibhat over 1 year ago
Submission Judgement Published Reason: Non-acceptable severity
Assigned finding tags:
single-step-ownership
informational/invalid
Prize pool breakdown
Total prize
20,000 USDC
nSLOC
60933 USDC / LOC
17,500 USDC
2,500 USDC
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.