Drive Crypto audit reports

Drive Crypto has 1 public audit report from CertiK; dated 21 Nov 2022; no critical findings reported. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm17

Statuses are the security firms’ own

17 findings are still open or acknowledged in the firms’ reports: 4 high, 3 medium, 10 low (10 open, 7 acknowledged).

High
4
Medium
3
Low
10
  • High Acknowledged

    Centralization Related Risks In AttributeMap.sol

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • High Acknowledged

    Centralization Related Risks In DriveCrypto.sol

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • High Acknowledged

    Centralization Risks in SwapHelper.sol

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • High Acknowledged

    Logic Issue On Function `burn()`

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • Medium Acknowledged

    Incorrect initialization Of the `_permissions`

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • Medium Acknowledged

    Initial Token Distribution

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • Medium Acknowledged

    Potential Loss of Rewards

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • Low Open

    Lack of reasonable boundary

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • Low Open

    Missing Receive Function

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

  • Low Open

    No Function To Disable Token

    Drive Crypto · CertiK · 21 Nov 2022 · Report ↗

All 17 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Drive CryptoSecurity firm: CertiKDate: Scope: 1 address on BNB ChainNone openFindings: 4 high · 4 medium · 10 low
1 fixed · 7 acknowledged · 10 open
skynet.certik.com ↗

Findings18

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical000
High040
Medium031
Low1000
LowLack of reasonable boundaryDrive Crypto · CertiK · 21 Nov 2022Open

The variables `_maxTxAmount`, `_maxAccountAmount`, `_minAmountToAutoSwap`, and `minTokenHoldToStake` do not have reasonable boundaries, so they can be given arbitrary values after deploying.

Open the report
LowMissing Receive FunctionDrive Crypto · CertiK · 21 Nov 2022Open

The owner account can call the function `safeWithdraw()` to withdraw all ETHs. However, there is no `receive()` or `fallback()` function in the SwapHelper.sol, so this contract cannot receive native tokens.

Open the report
LowNo Function To Disable TokenDrive Crypto · CertiK · 21 Nov 2022Open

The admin can call the function `enableToken()` to set the `pauseToken` to false, however, there is no function to set the `pauseToken` to true.

Open the report
LowPotential Flashloan AttackDrive Crypto · CertiK · 21 Nov 2022Open

Flash loans are a way to borrow large amounts of money for a certain fee. The requirement is that the loans need to be returned within the same transaction in a block. If not, the transaction will be reverted. An attacker can use the borrowed money as the initial funds for an exploit to enlarge the profit and/or manipulate the token price in the decentralized exchanges. We find that the function `executeSwap()` rely on price calculations that are based on-chain, meaning that they would be susceptible to flash-loan attacks by manipulating the price of given pairs to the attacker's benefit.

Open the report
LowPotential Gas ExhaustionDrive Crypto · CertiK · 21 Nov 2022Open

The `for` loop within the function `multiTransfer()` takes unbounded arrays' lengths as the maximum iteration times. If the size of the array `users` grows large, iterating through the entire array could be an expensive operation. Even worse, it could exceed the gas limit per block.

Open the report
LowPotential Sandwich AttacksDrive Crypto · CertiK · 21 Nov 2022Open

A sandwich attack might happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by frontrunning (before the transaction being attacked) a transaction to purchase one of the assets and make profits by backrunning (after the transaction being attacked) a transaction to sell the asset. The following functions are called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions are vulnerable to sandwich attacks, especially when the input amount is large: ```solidity=337 uint256 wbnbAmount = getAmountOut(totalAmount, reserve1, reserve0); swapToken(liquidityPair, reversed ? 0 : wbnbAmount, reversed ? wbnbAmount : 0, secondaryPairLocal); uint256 wbnbBalanceNew = getTokenBalanceOf(wbnbAddress, secondaryPairLocal); require(wbnbBalanceNew == wbnbBalanceBefore + wbnbAmount, "Wrong amount of swapped on WBNB"); ``` ```solidity=349 uint256 busdAmount = getAmountOut(amountOut, reserve1, reserve0); swapToken(secondaryPairLocal, reversed ? 0 : busdAmount, reversed ? busdAmount : 0, swapHelper); uint256 busdBalanceNew = getTokenBalanceOf(busdAddress, swapHelper); require(busdBalanceNew == busdBalanceBefore + busdAmount, "Wrong amount of swapped on BUSD"); amountOut = busdAmount; ```

Open the report
LowThird Party DependencyDrive Crypto · CertiK · 21 Nov 2022Open

The contract is serving as the underlying entity to interact with one or more third-party protocols. The scope of the audit treats third-party entities as black boxes and assumes their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=19 address constant private WBNB = 0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c; // BSC WBNB address constant private BUSD = 0xe9e7CEA3DedcA5984780Bafc599bD69ADd087D56; // BSC BUSD ``` ```solidity=88 PancakeRouter router = PancakeRouter(0x10ED43C718714eb63d5aA57B78B54704E256024E); // BSC ``` - The function `DriveCrypto.constructor` interacts with third party contract with `PancakeFactory` interface via `router`.

Open the report
LowUnchecked ERC-20 `transfer()`/`transferFrom()` CaDrive Crypto · CertiK · 21 Nov 2022Open

The return value of the transfer()/transferFrom() call is not checked. ```solidity=12 function safeTransfer(address token, address receiver, uint256 amount) external isWithdrawer { IERC20(token).transfer(receiver, amount); } ```

Open the report
LowUnused Return ValueDrive Crypto · CertiK · 21 Nov 2022Open

The return value of an external call is not stored in a local or state variable. ```solidity=11 function safeApprove(address token, address spender, uint256 amount) external isWithdrawer { IERC20(token).approve(spender, amount); } ``` --- ```solidity=11 function safeApprove(address token, address spender, uint256 amount) external onlyOwner { IERC20(token).approve(spender, amount); } ```

Open the report
LowVariables That Could Be Declared as ImmutableDrive Crypto · CertiK · 21 Nov 2022Open

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

Open the report

Contracts1

AddressChainSource code
0x61ccf5351d63b36ae2f7f4d0f0f9a65989c1de7dChain: BNB ChainSource code: Verified source

Drive Crypto: questions

Is Drive Crypto audited?

Trustblock holds 1 public audit report for Drive Crypto, dated 21 Nov 2022. The latest is by CertiK (“Drive Crypto”).

Who audited Drive Crypto?

CertiK wrote the report Trustblock holds for Drive Crypto.

Are there open findings in Drive Crypto’s audits?

17 findings are still open or acknowledged in the firms’ reports: 4 high, 3 medium, 10 low (10 open, 7 acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="drive-crypto"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something 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