Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate token security vulnerability #181

Closed
musnit opened this issue Apr 13, 2020 · 5 comments
Closed

Duplicate token security vulnerability #181

musnit opened this issue Apr 13, 2020 · 5 comments
Labels

Comments

@musnit
Copy link

musnit commented Apr 13, 2020

With the change to remove whitelisting, the bridge is now vulnerable to an attacker who can duplicate tokens:

An attacker can duplicate any ERC20 that has come across the bridge by creating a copy of that ERC20's contract on Ethereum and relaying over copied tokens. The copied tokens will be indistinguishable from originals on the Cosmos side due to this security vulnerability.

@okwme
Copy link
Contributor

okwme commented Apr 16, 2020

i thought we were name spacing by contract address to prevent this?

@musnit
Copy link
Author

musnit commented Apr 16, 2020

@okwme cosmos doesn't support long enough names to do this

@okwme
Copy link
Contributor

okwme commented Apr 16, 2020

I see your comment here discussing this: #123 (comment)

@jkbrooks
Copy link

jkbrooks commented May 18, 2020

@okwme Is this still an open now that #123 has been closed?

If not, let's remove the warning on the ReadMe. If so, what do we need to do to resolve the issue?

@musnit
Copy link
Author

musnit commented May 18, 2020

@jkbrooks still an issue. to resolve, would need to implement a custom token metadata module, either within the peggy codebase or for cosmos-sdk as a whole

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants