CertiK reviewed STYLE Protocol on 3 Jun 2024: 10 findings, 0 critical; 4 acknowledged, 6 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 | 3 | 0 |
| Medium | 0 | 1 | 0 |
| Low | 6 | 0 | 0 |
In the contract `VestingWalletHolder`, a state variable `_owner` is defined: ```solidity=1793 address private immutable _owner; ``` it is set during the deployment ```solidity=1843 constructor() { _vestingWalletImplementation = payable(address(new VestingWallet())); _owner = msg.sender; } ``` And it is never used even if an `onlyOwner` modifier is defined: ```solidity=1798 modifier onlyOwner() { if (_owner == msg.sender) { _; } else { revert ImproperOwner(); } } ```
A reentrancy attack can occur when the contract creates a function that makes an external call to another untrusted contract before resolving any effects. If the attacker can control the untrusted contract, they can make a recursive call back to the original function, repeating interactions that would have otherwise not run after the external call resolved the effects. *This finding is considered minor because the reentrancy only causes out-of-order events.* ### External call(s) ```solidity=1553 IERC20(token).safeTransfer(_beneficiary, releasable); ``` * This function call executes the following external call(s). * In `SafeERC20._callOptionalReturn`, * `returndata = address(token).functionCall(data)` * In `Address.functionCallWithValue`, * `(success,returndata) = target.call{value: value}(data)` ### Events emitted after the call(s) ```solidity=1555 emit ERC20Release(token, releasable); ``` --- ### External call(s) ```solidity=1636 Address.sendValue(payable(to), amount); ``` * This function call executes the following external call(s). * In `Address.sendValue`, * `(success,None) = recipient.call{value: amount}("")` ### Events emitted after the call(s) ```solidity=1638 emit EtherWithdraw(amount); ``` --- ### External call(s) ```solidity=1650 IERC20(token).safeTransfer(to, amount); ``` * This function call executes the following external call(s). * In `SafeERC20._callOptionalReturn`, * `returndata = address(token).functionCall(data)` * In `Address.functionCallWithValue`, * `(success,returndata) = target.call{value: value}(data)` ### Events emitted after the call(s) ```solidity=1652 emit ERC20Withdraw(token, amount); ``` --- ### External call(s) ```solidity=1860 IVestingWallet(clone).initialize(beneficiary, start, duration); ``` ### Events emitted after the call(s) ```solidity=1864 emit CreateVesting(clone); ```
A reentrancy attack can occur when the contract creates a function that makes an external call to another untrusted contract before resolving any effects. If the attacker can control the untrusted contract, they can make a recursive call back to the original function, repeating interactions that would have otherwise not run after the external call resolved the effects. *This finding is considered minor because the state variable is only incremented or decremented. So, the effect of out-of-order increments may be unobservable after transaction. However, the reentrancy vulnerability may still cause other issues in the middle of transaction.* ### External call(s) ```solidity=1860 IVestingWallet(clone).initialize(beneficiary, start, duration); ``` ### State variables written after the call(s) ```solidity=1861 _contracts[msg.sender][_vestingcounts[msg.sender]] = clone; ``` ```solidity=1862 ++_vestingcounts[msg.sender]; ```
The ERC777 standard is not recommended due to concerns regarding over-engineering, potential security vulnerabilities, and unnecessary complexity.
In `VestingWallet.initialize()`, no check is made on the `_beneficiary` address.
The smart contract contains one or more inteface definitions that are not used, which can lead to unnecessary complexity and reduced maintainability. ```solidity=1127 interface IERC20Permit { ``` - `IERC20Permit` is declared but never used.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (2)
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