Q1 2025 Web3 Security ReportAccess control failures led to $1.63 billion in losses
Discover report insights
  • Hacken
  • Audits
  • cratd2c
  • [SCA] CratD2C / Token / Jan2024
CratD2C logo

CratD2C

Audit name:

[SCA] CratD2C / Token / Jan2024

Date:

Feb 19, 2024

Table of Content

→Introduction
→Audit Summary
→Document Information
→System Overview
→Executive Summary
→Risks
→Findings
→Appendix 1. Severity Definitions
→Appendix 2. Scope
→Disclaimer

Want a comprehensive audit report like this?

Introduction

We express our gratitude to the CratD2C team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

CratD2C represents a pioneering platform in the blockchain space, combining the robustness of Delegated Proof of Stake (DPoS) with Layer-1 architecture to achieve a new standard in security, speed, and scalability. At its core, CratD2C transforms e-commerce by facilitating direct connections between businesses and consumers. This is achieved through a secure, transparent, cost-effective smart contract system built on its DPoS blockchain framework.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC20
Timeline01/02/2024 - 26/02/2024
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/samaros/CratD2C→
    Commitb405b593eac47ccf370d72cbe450209b4b822aa8

    Audit Summary

    Total9.1/10
    Security Score

    10/10

    Test Coverage

    94.74%

    Code Quality Score

    8/10

    Documentation Quality Score

    7/10

    7Total Findings
    6Resolved
    1Accepted
    0Mitigated

    The system users should acknowledge all the risks summed up in the risks section of the report

    Document Information

    This report may contain confidential information about IT systems and the intellectual property of the Customer, as well as information about potential vulnerabilities and methods of their exploitation.

    The report can be disclosed publicly after prior consent by another Party. Any subsequent publication of this report shall be without mandatory consent.

    Document

    NameSmart Contract Code Review and Security Analysis Report for CratD2C
    Audited ByTurgay Arda Usman
    Approved ByGrzegorz Trawinski
    Websitehttps://cratd2claunch.pro→
    Changelog05/02/2024 - Preliminary Report & 26/02/2024 - Final Report

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for CratD2C
      Audited By
      Turgay Arda Usman
      Approved By
      Grzegorz Trawinski
      Website
      https://cratd2claunch.pro→
      Changelog
      05/02/2024 - Preliminary Report & 26/02/2024 - Final Report

    System Overview

    CratD2C represents a pioneering platform in the blockchain space, combining the robustness of Delegated Proof of Stake (DPoS) with Layer-1 architecture to achieve a new standard in security, speed, and scalability. At its core, CratD2C transforms e-commerce by facilitating direct connections between businesses and consumers. This is achieved through a secure, transparent, cost-effective smart contract system built on its DPoS blockchain framework. It has the following contracts:

    CratToken  — simple ERC-20 token that mints all initial supply to a deployer.

    It has the following attributes:

    • Name: CratD2C-Pre.

    • Symbol: CratD2C-Pre.

    • Decimals: 18.

    • Total supply: 20M tokens.

    CratCrowdsale — a contract that handles the crowd sale for the ICO.

    Privileged roles

    • The owner of the CratCrowdsale contract can withdraw ERC20 tokens from the contract.

    • The owner of the CratCrowdsale contract can pause the contract.

    • The owner of the CratCrowdsale contract can update the referral -refund the interest.

    • The admin can transfer Crat tokens.

    • The crowd sale can transfer Crat tokens.

    • The bridge can transfer Crat tokens.

    Executive Summary

    Documentation quality

    The total Documentation Quality score is 7 out of 10.

    • Functional requirements are partially provided.

    • The technical description is partially provided.

    Code quality

    The total Code Quality score is 8 out of 10.

    • The code mostly follows the style guides and best practices.

    • The deployment instructions are not provided

    • The development environment is configured.

    Test coverage

    Code coverage of the project is 94.74% (branch coverage).

    • Deployment and basic user interactions are covered with tests.

    • Interactions by several users are  tested thoroughly.

    Security score

    Upon auditing, the code was found to contain 2 critical, 0 high, 3 medium, and 0 low severity issues, leading to a security score of 10 out of 10.

    All identified issues are detailed in the “Findings” section of this report.

    Summary

    The comprehensive audit of the customer's smart contract yields an overall score of 9.1. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Risks

    The owner of the CratCrowdsale.sol contract can transfer any amount of ERC20 tokens any time without notifying anyone.

    Referrer bonuses are being deducted from the buyer as extra funds. This means that the users have to these amounts separately.

    Findings

    Code
    ―
    Title
    Status
    Severity
    F-2024-0768Erroneous Decimal Handling in Token Purchase Function
    fixed

    Critical
    F-2024-0757Wrong Initial Supply Amount
    fixed

    Critical
    F-2024-0758Missing Cap Limit Check
    fixed

    Medium
    F-2024-0756The Owner Can Frontrun the User's Transaction
    fixed

    Medium
    F-2024-0755Refund Interest Rate Can be Frontrunned
    fixed

    Medium
    F-2024-0754Redundant Function
    accepted

    Observation
    F-2024-0751Missing Zero Address Validation
    fixed

    Observation
    1-7 of 7 findings

    Identify vulnerabilities in your smart contracts.

    Appendix 1. Severity Definitions

    When auditing smart contracts, Hacken is using a risk-based approach that considers Likelihood, Impact, Exploitability and Complexity metrics to evaluate findings and score severities.

    Reference on how risk scoring is done is available through the repository in our Github organization:

    Severity

    Description

    Critical
    		Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.

    High
    		High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.

    Medium
    		Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.

    Low
    		Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution, do not affect security score but can affect code quality score.

    • Severity

      Critical

      Description

      Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.

      Severity

      High

      Description

      High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.

      Severity

      Medium

      Description

      Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.

      Severity

      Low

      Description

      Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution, do not affect security score but can affect code quality score.

    Appendix 2. Scope

    The scope of the project includes the following smart contracts from the provided repository:

    Contracts in Scope

    contracts
    CratCrowdsale.sol - contracts/CratCrowdsale.sol
    CratToken.sol - contracts/CratToken.sol
    interfaces
    ICratCrowdsale.sol - contracts/interfaces/ICratCrowdsale.sol

    Disclaimer