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

A logical bug in the NAME_SERVICE_BANK contract #32

Open
letonchanh opened this issue Jul 17, 2024 · 1 comment
Open

A logical bug in the NAME_SERVICE_BANK contract #32

letonchanh opened this issue Jul 17, 2024 · 1 comment

Comments

@letonchanh
Copy link

Besides the bug targeted by the NameServiceBank challenge, there is another logical flaw in the NAME_SERVICE_BANK contract that allows an attacker to steal the funds of a user whose username was set with a non-zero obfuscation degree. This logical bug is independent of the Solidity version, meaning the vulnerability exists regardless of the compiler used. It could be interesting to create a new NameServiceBank2 challenge that exploits this specific bug.

I can discuss the details offline.

@wafardev
Copy link

Hey! Can we discuss how to resolve the NameServiceBank challenge? Thanks!

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

No branches or pull requests

2 participants