ETH_iOWNToken_audit_report.md

iOWN Token audit report.

1. Summary

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

2. In scope

Сommit hash c559f9ee36f1da2b9fd520a0200ee43b95ac848c.

• CappedBurnableToken.sol.
• IownToken.sol.
• Migrations.sol.
• TokenTreasury.sol.
• TransfererRole.sol.
• UpgradeableToken.sol.
• UpgradeAgent.sol.

3. Findings

In total, 3 issues were reported including:

• 0 medium severity issues
• 1 low severity issues
• 2 owner privileges (ability of owner to manipulate contract, may be risky for investors)..
• 0 notes.

No critical security issues were found.

3.1. 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) );

3.2. Owner Privileges

Severity: owner previliges

Description

Contract owner allow himself to:

• Owner can upgrade contract and implement any logic in the new contract. And even if the new contract will be audited, at any time possible to change the address of the new contract again to not audited and insecure here.

• Pause/unpause upgrade tokens here.

4. Conclusion

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