The setCurveVault
function doesn't implement all the needed checks it needs to avoid vulnerabilities
The setCurveVault
only implements a zero check as seen here
Compare this to the `setStabilityPool` function that implements a zero address check alongside a check making sure that the oldStabilityPool != the new stabilityPool being passed in as a parameter
This would cause the old CurveVault to still remain and the function would still execute like it's changed
Manual Analysis
Add a check that ensures that oldCurveVault != newCurveVault
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.