- Hacken
- Audits
- united-atlas
- [SCA] United Atlas | United-Atlas-Contracts | Nov2024
Audit name:
[SCA] United Atlas | United-Atlas-Contracts | Nov2024
Date:
Nov 29, 2024
Table of Content
Introduction
We express our gratitude to the United Atlas team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
United Atlas is a travel platform integrating with blockchain to offer cryptocurrency payments and tokenized timesharing, . Its token, UAT, is utilized for booking travel services, purchasing timesharing slots, creating and trading NFTs, gamification, and staking.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for United Atlas |
| Audited By | , Adam Idarrha |
| Approved By | Ataberk Yavuzer |
| Website | https://unitedatlas.io/→ |
| Changelog | 18/11/2024 - Preliminary Report |
| 29/11/2024 - Final Report | |
| Platform | Polygon |
| Language | Solidity |
| Tags | Upgradeable Proxy, ERC-20 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for United Atlas
- Audited By
- , Adam Idarrha
- Approved By
- Ataberk Yavuzer
- Website
- https://unitedatlas.io/→
- Changelog
- 18/11/2024 - Preliminary Report
- 29/11/2024 - Final Report
- Platform
- Polygon
- Language
- Solidity
- Tags
- Upgradeable Proxy, ERC-20
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Repository | https://github.com/UnitedAtlas/UnitedAtlas/→ |
| File Hash | sha3-224: b81f9185dec22c10c005d64d33a5c178b585d2727a5c17f94c3078d4 |
Review Scope
- File Hash
- sha3-224: b81f9185dec22c10c005d64d33a5c178b585d2727a5c17f94c3078d4
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
Documentation quality
Functional requirements are complete.
Technical description is sufficient.
Code quality
The code mostly conforms with the Solidity Style Guide.
System Overview
United Atlas is a protocol with the following contracts:
UnitedAtlas — simple ERC-20 token that mints all initial supply to the owner, with burnable functionality. Additional minting is not allowed.
It has the following attributes:
Name: UnitedAtlas
Symbol: UAT
Decimals: 18
Total supply: 8 billion tokens.
Privileged roles
The owner of the UnitedAtlas contract can arbitrarily update the code of the contract through upgrading it.
Potential Risks
Centralization Risk: The contract mints the entire token supply to the owner upon deployment, creating a significant centralization risk. This concentration of tokens in a single address gives the owner disproportionate control over the token's distribution and potentially the protocol's governance.
Upgradeability: Upgradeable contracts typically rely on an upgrade mechanism controlled by one or more addresses, introducing centralization and potentially creating single points of failure or trust.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2024-7197 | Floating pragma | fixed | Observation | |
| F-2024-7196 | Use Ownable2Step rather than Ownable | fixed | Observation | |
| F-2024-7195 | Redundant override function | fixed | Observation | |
| F-2024-7163 | remove initializer modifier from the constructor | fixed | Observation | |
| F-2024-7162 | Missing _disableInitializers() in Upgradable Contract Constructor | fixed | Observation |
Appendix 1. Definitions
Severities
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. |
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.
Potential Risks
The "Potential Risks" section identifies issues that are not direct security vulnerabilities but could still affect the project’s performance, reliability, or user trust. These risks arise from design choices, architectural decisions, or operational practices that, while not immediately exploitable, may lead to problems under certain conditions. Additionally, potential risks can impact the quality of the audit itself, as they may involve external factors or components beyond the scope of the audit, leading to incomplete assessments or oversight of key areas. This section aims to provide a broader perspective on factors that could affect the project's long-term security, functionality, and the comprehensiveness of the audit findings.
Appendix 2. Scope
The scope of the project includes the following smart contracts from the provided repository:
Scope Details | |
|---|---|
| Repository | N/A |
| Commit | sha3-224: b81f9185dec22c10c005d64d33a5c178b585d2727a5c17f94c3078d4 |
| Deployed Address | Polygon: 0x8b86Ff51C70c67D06CD4Cf41b4d0B4a4bBC8D842 |
| Whitepaper | https://docsend.com/view/pxpne22zdseezyuy→ |
| Requirements | N/A |
| Technical Requirements | N/A |
Scope Details
- Repository
- N/A
- Commit
- sha3-224: b81f9185dec22c10c005d64d33a5c178b585d2727a5c17f94c3078d4
- Deployed Address
- Polygon: 0x8b86Ff51C70c67D06CD4Cf41b4d0B4a4bBC8D842
- Requirements
- N/A
- Technical Requirements
- N/A