Skip to content

Instantly share code, notes, and snippets.

@yuriy77k
Forked from MrCrambo/ETH_Curate_report.md
Created August 16, 2019 08:00
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save yuriy77k/515f895dfb06b566c0a99478a333b0fd to your computer and use it in GitHub Desktop.
Save yuriy77k/515f895dfb06b566c0a99478a333b0fd to your computer and use it in GitHub Desktop.

Summary

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

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

In scope

  1. https://etherscan.io/address/0x490dbf7884b8e13c2161448b83dd2d8909db48ed#code

Findings

In total, 2 issues were reported including:

  • 0 high severity issues.

  • 0 medium severity issues.

  • 0 owner privilegies issues.

  • 2 low severity issues.

  • 0 notes.

Security issues

1. Zero address checking

Severity: low

Description

In functions transfer and transferFrom there is no zero address checking. And function totalSupply will show wrong balance without zero address balance.

Recommendation

Add zero address checking

require(to != address(0));

2. Known vulnerabilities of ERC-20 token

Severity: low

Description

It is possible to double withdrawal attack. More details here

Recommendation

Add increaseApproval and decreaseApproval functions

Conclusion

Smart contract is safe.

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