Vesu Protocol Security Review
Audit · firm’s term: security review
Cairo Security Clan reviewed Vesu (Vesu Protocol Security Review) on 12 Feb 2024: 2 findings, 0 critical; all marked fixed.
Trustblock does not review code.
Findings2
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 | 0 | 0 | 2 |
LowDefine singleton dispatcher when using repeatedlyFixed
In the function add_asset, the singleton dispatcher variable is defined but not used in the first external call to set_asset_config, only in modify_position. It is recommended to define the singleton dispatcher above and use it in both calls.
LowUnchecked return values of ERC20 transferFixed
In the codebase, ERC20 transfers using transferFrom return a boolean indicating success, but the return values are not checked. This may cause unexpected behavior if the token does not revert on failure.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (12)
- srcvendorchainlink.cairo
- srcextensioncomponentsposition_hooks.cairo
- srcextensiondefault_extension_po.cairo
- contracts1
- srcextensioncomponentschainlink_oracle.cairo
- srclib.cairo
- srcv_token.cairo
- srcextensioncomponentsfee_model.cairo
- srcextensioncomponentsinterest_rate_model.cairo
- srcextensiondefault_extension_cl.cairo
- srcunits.cairo
- srcextensioncomponentstokenization.cairo
Part of Vesu’s security record
VesuSecurity firm
Cairo Security Clan13 projects reviewed · 21 reports · latest Sep 2025
See Cairo Security Clan’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