SmartVaultManagerV5 does not have collateralRate setter
Summary
SmartVaultManagerV5 does not have collateralRate setter, which can either inhibit protocol or lead to user loss of funds.
Vulnerability Details
collateralRate is neither not set in constructor, nor does it have a setter function, like other parameters of the protocol, e.g. rates. It means it has default value of 0, which can lead to negative consequences.
Impact
If used in proxying, this can lead to contract redeployment.
If deployed anew/raw, users can send funds with intention to mint() stablecoins, but they won't be able to since 0 collateralRate will lead to 0 division error in maxMintable() function in SmartVaultV3.
Tools Used
Manual
Recommendations
Implement setters/default value for collateralRate, depending on intention.
Lead Judging Commences
informational/invalid
Prize pool breakdown
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.