Audit name:
[SCA] Cogito | ERC20 | May2023
Date:
May 11, 2023
Table of Content
Introduction
We express our gratitude to the Cogito team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
Cogito's mission is to bring tokenized traditional assets onchain for increased liquidity, security, and transparency. Led by a team of finance and technology experts, Cogito is well-positioned to build the future of finance onchain.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20 |
| Timeline | 02/05/2023 - 12/05/2023 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/cogitoprotocol/cogito-token-contracts→ |
| Commit | 0de1aeac34d6 |
Review Scope
- Commit
- 0de1aeac34d6
Audit Summary
10/10
87.5%
9/10
10/10
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 | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for Cogito |
| Audited By | Hacken |
| Website | https://www.cogitoprotocol.com/→ |
| Changelog | 12/05/2023 - Initial Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Cogito
- Audited By
- Hacken
- Changelog
- 12/05/2023 - Initial Review
System Overview
Cogito is a staking protocol with the following contracts:
CogitoGovernanceToken — a ERC-20 token that allows minting and burning tokens, implements pausable mechanism.
It has the following attributes:
Name: TokenName
Symbol: TST
Decimals: 6
Privileged roles
CogitoGovenanceToken.sol:
Minter: can mint token.
Pauser: can pause and unpause the smart contract.
Default admin: can set roles, after deploying, has minter and pauser access.
Executive Summary
Documentation quality
The total Documentation quality score is 10 out of 10.
Functional requirements are detailed.
Project overview is detailed
All roles in the system are described.
Use cases are described and detailed.
Technical description is robust.
Run instructions are provided.
Technical specification is provided.
NatSpec sufficient.
Code quality
The total Code quality score is 9 out of 10.
Best practice violations.
Test coverage
Code coverage of the project is 87.5% (branch coverage).
Deployment and basic user interactions are covered with tests.
Security score
Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 1 low severity issues. Out of these, 0 issues have been addressed and resolved, 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.8. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2023-0108 | Gas Optimization - Functions that Can Be Declared External | unfixed | Low | |
| I-2023-0012 | Redundant Import | unfixed | Observation |
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 | |
|---|---|
| Repository | https://github.com/cogitoprotocol/cogito-token-contracts→ |
| Commit | 0de1aeac34d6 |
| Whitepaper | Provided→ |
| Requirements | Provided→ |
| Technical Requirements | Provided→ |