- Hacken
- Audits
- kyber-network
- [SCA] Kyber Network | ERC20 | May2021
Audit name:
[SCA] Kyber Network | ERC20 | May2021
Date:
May 19, 2021
Table of Content
Introduction
We express our gratitude to the Kyber Network team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
| title | content |
|---|---|
| Platform | Ethereum, BNB Chain, Arbitrum, Polygon, Fantom, Avalanche, Optimism, Solidity |
| Language | Solidity |
| Tags | ERC-20 |
| Timeline | 10/05/2021 – 18/05/2021 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/KyberNetwork/kyber_protocol_sc/blob/6c2295ac36eb88bf5933f01dc135707ba9653431/contracts/sol6/token→ |
| Commit | 6c2295ac36eb88bf5933f01dc135707ba9653431 |
Review Scope
- Commit
- 6c2295ac36eb88bf5933f01dc135707ba9653431
Audit Summary
According to the assessment, the Customer's smart contracts are well-secured.
Our team performed an analysis of code functionality, manual audit, and automated checks with Mythril and Slither. All issues found during automated analysis were manually reviewed, and important vulnerabilities are presented in the Audit overview section. All found issues can be found in the Audit overview section.
Security engineers found no issues during the first review.
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 Kyber Network |
| Audited By | Hacken |
| Approved By | Hacken |
| Changelog | 18/05/2021 – Initial Audit |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Kyber Network
- Audited By
- Hacken
- Approved By
- Hacken
- Changelog
- 18/05/2021 – Initial Audit
System Overview
Conclusion
Smart contracts within the scope were manually reviewed and analyzed with static analysis tools.
Audit report contains all found security vulnerabilities and other issues in the reviewed code.
Security engineers found no issues during the first review.
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/KyberNetwork/kyber_protocol_sc/blob/6c2295ac36eb88bf5933f01dc135707ba9653431/contracts/sol6/token→ |
| Commit | 6c2295ac36eb88bf5933f01dc135707ba9653431 |
| Deployed contract | https://etherscan.io/address/0xdeFA4e8a7bcBA345F687a2f1456F5Edd9CE97202#codex→ |
| https://etherscan.io/address/0xe5e8e834086f1a964f9a089eb6ae11796862e4ce#code→ |
Scope Details
- Commit
- 6c2295ac36eb88bf5933f01dc135707ba9653431