2

In May 2017, an "attacker" created a contract that attempts to create many other contracts(using many JUMPDEST operations in the creation bytecode) until it runs out of gas.

I see the gas improvemnts of EIP-150, but don't see where this attack would be mitigated today.

Is this "attack" still possible?

One of the txs

Reddit thread

Improve this question
2
  • After reading the Reddit thread I still don't understand the attack vector. Who gains and how?
    – Lauri Peltonen
    Commented Jun 25, 2020 at 17:07
  • I believe it was an attempted DoS
    – Bert Kellerman
    Commented Jun 25, 2020 at 19:24

1 Answer 1

Reset to default
3

From this reddit message it was fixed in geth 1.6.5 https://www.reddit.com/r/ethereum/comments/6ene3u/the_attacker_is_back_account_related_to_devcon2/

Pull request with the fix: https://github.com/ethereum/go-ethereum/pull/14570

core/vm: Use a bitmap instead of a map for jumpdest analysis

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.