Skip to content

Instantly share code, notes, and snippets.

@yuriy77k
Forked from MrCrambo/ETH_Lutoken_report.md
Created May 20, 2019 16:24
Show Gist options
  • Save yuriy77k/b80c07a36e5c276351c89c3bb535aab7 to your computer and use it in GitHub Desktop.
Save yuriy77k/b80c07a36e5c276351c89c3bb535aab7 to your computer and use it in GitHub Desktop.

Summary

This is the report from a security audit performed on Lutoken by MrCrambo.

The audit focused primarily on the security of Lutoken smart contract.

In scope

  1. https://github.com/CINEMADROM/SMART-CONTRACT/blob/master/LUTOKEN.sol

Findings

In total, 3 issues were reported including:

  • 0 high severity issues.

  • 0 medium severity issues.

  • 1 owner privilegies issues.

  • 2 low severity issues.

Security issues

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. More details here

Recommendation

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

require( _to != address(this) );

2. Owner privilegies

Severity: owner privilegies

Description

  1. Owner can pause transfers any time he wants.
  2. Owner can freeze at any time he wants.

3. Zero address checking

Severity: low

Description

There is no zero address checking in constructor

Conclusion

Smart contract contains low severity issues.

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