That's actually hilarious.
Samba on Linux with defaults is also vulnerable to SMBLoris because smbd forks for each client. Fix: "max smb processes = 1000" in smb.conf.pic.twitter.com/vA9XW16j8S
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Nice find, have you notified the http://smbloris.com authors about that?
-
Pinging
@zerosum0x0 and@JennaMagius. Not sure if they set up the site though.
End of conversation
New conversation -
-
-
Np! You may also want to update the "attack cost" section, it's not quite right in practice:https://twitter.com/marcan42/status/892794394805288960 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The max forks config isn't set by default? And is not limited by ulimits in a default install?
-
It defaults to 0 = unlimited, which is stupid. ulimit settings vary by distro, but don't seem to work for me (maybe because it runs as root)
- Show replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
For the record, my math was 18B Eth + 20B IP + 20B TCP = 58B, ×2 packets (SYN+ACK), +4 payload = 120 bytes/connection TX. RX would be ~½.
-
Also note that the Samba issue isn't due to the header, it's just general process memory overhead. You can exploit it w/o sending data.
- Show replies
New conversation -
-
-
Yeah, this is basically the good old forking daemon DoS. It's existed for decades, but some stuff still doesn't ship with process limits...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.