15,000 USDC
View results
Submission Details
Severity: low

Lack of non-reentrant modifier in burnDsc() function

Summary

While protocol has implemented non-reentrant modifier for all the function interacting with other contracts there is not one for burnDsc()

Vulnerability Details

It is good practise to implemented non-reentrant modifier for any state changing function interacting with the other contract along with check-effect-integration pattern.

The protocol has implemented the same for all the functions except for burnDsc() function.

Impact

Potential for reentrancy via burnDSC() function.

Tools Used

Manual Review

Recommendations

Implement non-reentrant modifier for the burnDsc() function.

Support

FAQs

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