Very interesting. Yes, I think rate limiting on both sides is necessary.
This is an excellent fuzzing method.
I tried running chorus and hitting it with this attack from a local process. For about 100,000 bytes (in 0.031 seconds) chorus handles and prints all the errors, generally being JSON parse errors. Then a bug is hit and I get a thread panic (chorus main thread continues, only that one connection is dropped)
Also chorus has mechanisms to drop connections and block IPs based on too many errors coming in, but for some reason these didn't work against this.
This is Sunday I wasn't going to do dev work today, but this is too interesting.
M. Dilger /
npub1ac…9p35c
2024-07-13 23:42:51
in reply to nevent1q…y4g5
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35cPublished at
2024-07-13 23:42:51Event JSON
{
"id": "f2bb6b0d208f894f84ebbf65951e37f39d0965ffd315e118d0ff8e81014ca7c8",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1720906971,
"kind": 1,
"tags": [
[
"p",
"0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd"
],
[
"e",
"667ba8d7229bfe28d077638b7e9cfd20b8df4f6958ef801962d308207d15ff43",
"wss://relay.mostr.pub/",
"root"
]
],
"content": "Very interesting. Yes, I think rate limiting on both sides is necessary.\n\nThis is an excellent fuzzing method.\n\nI tried running chorus and hitting it with this attack from a local process. For about 100,000 bytes (in 0.031 seconds) chorus handles and prints all the errors, generally being JSON parse errors. Then a bug is hit and I get a thread panic (chorus main thread continues, only that one connection is dropped)\n\nAlso chorus has mechanisms to drop connections and block IPs based on too many errors coming in, but for some reason these didn't work against this.\n\nThis is Sunday I wasn't going to do dev work today, but this is too interesting.",
"sig": "5f6993377b044d87e13a5522157da771e4b49bdb200a7ed3efd5b411aa9cabac4dcefb235aad12599ea12b1aeed6b93b49074588e7f67a60da4feca853a14bda"
}