Skip to content

Instantly share code, notes, and snippets.

@yuriy77k
Forked from danbogd/ETH_AsureToken_audit_report.md
Created April 30, 2019 08:42
Show Gist options
  • Save yuriy77k/0102e9e8cc41043bf2e1a56e92ee1531 to your computer and use it in GitHub Desktop.
Save yuriy77k/0102e9e8cc41043bf2e1a56e92ee1531 to your computer and use it in GitHub Desktop.

Asure Token audit report.

1. Summary

This document is a security audit report performed by danbogd, where Asure Token has been reviewed.

2. In scope

Сommit hash 50cfbe81c88ba9be85419cc191298872435c4615.

3. Findings

In total, 3 issues were reported including:

  • 1 medium severity issues
  • 1 owner privileges
  • 1 low severity issues.

No critical security issues were found.

3.1. Inconsistencies with Asure Token Generation Event.

Severity: Medium

Description

  1. According to the whitepaper, specified parameters of soft cup and hard cap, but in code we can't see these functions.

  2. According to the [whitepaper] the Asure Team and Advisors will receive their tokens over two years afterthe start of the second phase, but in constructor of AsureCrowdsaleDeployer contract we can't see the Teams and Advisor vesting parameters.

  3. According to the [whitepaper] the minimum Contribution is $ 100 (ETH equivalent), but we can't see this parameter in code.

3.2. Owner Privileges

Severity: owner privileges

Description

The contract owner allow himself to:

  • update bonus rate, bonus time, croudsale time and default rate before crowdsale opened.

  • withdraw ETH and tokens funds before the end of sales.

The contract is managed manually by the owner which is not good for investors.

3.3. Known vulnerabilities of ERC-20 token

Severity: low

Description

  1. It is possible to double withdrawal attack. More details here.

  2. Lack of transaction handling mechanism issue. WARNING! This is a very common issue and it already caused millions of dollars losses for lots of token users! More details here.

Recommendation

Add into a function transfer(address _to, ... ) following code:

require( _to != address(this) );

4. Conclusion

The review did not show any critical issues, some of medium and low severity issues were found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment