Part of CertiK’s series
CertiK reviewed Venus Protocol (Venus - VAI Controller Upgrade) on 26 Apr 2024: 6 findings, 0 critical; 5 marked fixed, 1 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 1 | 0 | 5 |
The function `liquidateVAI()` makes the following check: ```solidity require(!comptroller.protocolPaused(), "protocol is paused"); ``` as opposed to using `_ensureNotPaused()`.
Functions `mintVAI()` and `repayVAIFresh()` change how certain errors are handled, moving from returning an error to reverting. Protocols may be designed to interact and handle errors in a specific manner, causing issues with compatibility.
Function `repayVAIBehalf()` does not ensure that the input address `borrower` is not `address(0)`.
The function, `repayVAI()`, returns `repayVAIFresh()` which has been changed to return the `repaidAmount` as opposed to the `burn` value. While this change was implemented to fix an error in the logic of `liquidateVAIFresh()`, it changes the return value of an external-facing function. Consequently, a protocol that utilizes the return value of this function may have their logic broken by this change.
- The comments above functions `repayVAI()` and `repayVAIBehalf()` contain the following statement: "The repay function transfers VAI into the protocol and burn, reducing the borrower's borrow balance." The statement may read better as "The repay function transfers VAI interest into the protocol and burns the rest, reducing the borrower's borrow balance." - The following comment above function `repayVAI()` is also relevant to `repayVAIBehalf()`: "Before repaying an asset, users must first approve the VAI to access their VAI balance."
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (1)
1,045 projects reviewed · 1,376 reports · latest May 2025
See CertiK’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us