Q1 2025 Web3 Security ReportAccess control failures led to $1.63 billion in losses
Discover report insights
  • Hacken
  • Audits
  • wow-earn
  • [SCA] Wow Earn / Token / Dec2023
Wow Earn logo

Wow Earn

Audit name:

[SCA] Wow Earn / Token / Dec2023

Date:

Dec 28, 2023

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 thank Wow Earn for allowing us to conduct a Smart Contract Security Assessment. This document outlines our methodology, limitations, and results of the security assessment.

Wow Earn aims to build a seamless connection between users and the blockchain world web3 Platform by providing healthy and sustainable blockchain application.

titlecontent
PlatformEVM
LanguageSolidity
TagsVesting, reward distribution
Timeline11/12/2023 - 12/01/2024
Methodologyhttps://hackenio.cc/sc_methodology→

    Last Review Scope

    Repositoryhttps://github.com/ullaniubility/ulla-contract→
    Commitab46260719de5ca70cee6dad21336bc81b274ae9

    Audit Summary

    Total9.4/10
    Security Score

    10/10

    Test Coverage

    76,92%

    Code Quality Score

    8/10

    Documentation Quality Score

    8/10

    22Total Findings
    10Resolved
    12Accepted
    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 Wow Earn
    Audited ByGrzegorz Trawinski
    Approved ByPrzemyslaw Swiatowiec, Ataberk Yavuzer
    Websitehttps://www.wowearn.com/→
    Changelog12/01/2024 - Final Report

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for Wow Earn
      Audited By
      Grzegorz Trawinski
      Approved By
      Przemyslaw Swiatowiec, Ataberk Yavuzer
      Website
      https://www.wowearn.com/→
      Changelog
      12/01/2024 - Final Report

    System Overview

    The mineWOW contract is a centralised solution where privileged account can add and configure users that will have rewards accounted over time. Rewards are accounted in the form of native assets. Users can obtain rewards proportionally, issued over time.

    Privileged roles

    The mineWOW's owner can:

    • Register or re-register new user.

    • Distribute reward to the user.

    • Set essential state variables, e.g. unlock time.

    • Transfer ownership to another account.

    Executive Summary

    Documentation quality

    The total Documentation Quality score is 8 out of 10.

    Code quality

    The total Code Quality score is 8 out of 10.

    • No development environment configuration was provided.

    • Few observations were reported regarding redundant code items.

    • Few observations were reported regarding Gas extensive usage.

    • Few instances of inaccurate naming of function and variables where identified.

    Test coverage

    Code coverage of the project is 76,92% (branch coverage).

    Security score

    Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 6 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.4. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Risks

    The mineWOW contract is heavily centralised solution. Users have no control over protocol configuration. The rewards are distributed only to the users configured by the privileged account.

    Findings

    Code
    ―
    Title
    Status
    Severity
    F-2023-0157The amount() function can return inaccurate value
    accepted

    Low
    F-2023-0155Lack of two-step ownership transfer
    fixed

    Low
    F-2023-0154The totalCumulative state variable can be calculated only once
    accepted

    Low
    F-2023-0153The start() function lacks input validation
    fixed

    Low
    F-2023-0147Missing input validation for key parameters
    accepted

    Low
    F-2023-0143The lastTime() function can revert due to arithmetic underflow
    fixed

    Low
    F-2023-0175Redundant input parameter within the calculateDay() function
    fixed

    Observation
    F-2023-0174Gas over-consumption in loops
    fixed

    Observation
    F-2023-0171Unused State Variables
    fixed

    Observation
    F-2023-0170Constant variables can be introduced
    fixed

    Observation
    1-10 of 22 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:

    Scope Details

    Repositoryhttps://github.com/ullaniubility/ulla-contract→
    Commitab46260719de5ca70cee6dad21336bc81b274ae9
    WhitepaperNot provided.
    RequirementsNot provided.
    Technical RequirementsNot provided.

    Contracts in Scope

    ./src/mineWOW.sol

    • Contracts in Scope

      ./src/mineWOW.sol

    The scope provided for remediation phase is as follow:

    Scope Details

    Repositoryhttps://github.com/ullaniubility/ulla-contract→
    Commit948570380834c8450924584aba6998874a17d0cc
    WhitepaperNot provided.
    RequirementsNot provided.
    Technical RequirementsNot provided.

    Contracts in Scope

    src
    mineWOW.sol - src/mineWOW.sol

    Disclaimer