0-conf possible attack using large transactions

Question

0-conf possible attack using large transactions

cmaves opened this issue 7 years ago · 5 comments

By making a very simple modification to the monero-wallet-rpc, one can generate a valid low priority transaction that is small enough to be relayed, but large enough to never be confirmed by the network. After looking through the code. I looked through the code and I didn't see a protection against this kind of attack.

After 24 hours this transaction will drop from the mempool and the sender will be able to use the Monero again.

Answer 1 · 2018-01-25T04:46:10.000Z

This could be a mempool spam attack against the daemon itself. Don't you think it's worth reporting upstream, with some more details on how to perform it?

Answer 2 · 2018-01-26T21:16:50.000Z

I agree, transactions like this shouldn't be propagated through the network.

Answer 3 · 2018-01-26T21:30:50.000Z

I made an issue on the monero repo.
monero-project/monero#3189

Answer 4 · 2018-01-26T21:32:18.000Z

I'll leave this issue open until it is either fixed on the upstream or fixed in kasisto itself

Answer 5 · 2018-01-27T10:46:08.000Z

@cmaves In the future, please respect responsible disclosure by using using Monero's Vulnerability Response Process regardless of whether this issue is a confirmed vulnerability or not. Thank you.