I wrote a little poc of this myself, also i tryed udpsz -l 1 -b a -C ffffffff6c SERVER PORT -1
It sure fills the serverconsole with a2c_print stuff, but i dont see it lagging the server or even crashing it.
Any news on this one? Is it fixed or do i have to protect my servers?
-------
Edit:
I got my hands on this Oopscrasher sabados mentioned, but i dont see this one "exploiting" the a2c_print flaw.
It sure laggs the Server as hell, but to be honest i cant tell why.
Heres one of the packets it sends
Code:
0000 00 1a 4f fe 07 1d 00 1b fc f5 ce 5e 08 00 45 00 ..O........^..E.
0010 00 2e 01 6c 00 00 80 11 ca e3 c0 a8 03 1d 55 55 ...l..........UU
0020 55 55 08 af 69 87 00 1a 50 71 33 42 45 21 6f 64 UU..i...Pq3BE!od
0030 79 36 53 41 4d 50 42 45 21 64 69 69 y6SAMPBE!dii
So it basicly just spammes the server with
Code:
\x33\x42\x45\x21\x6f\x64\x79\x36\x53\x41\4d\x50\x42\x45\x21\64\x69\x69
which translates to
BE!ody6SAMPBE!dii
Regarding to
http://developer.valvesoftware.com/wiki/Server_queriesany packet to a source server should start with \xff\xff\xff\xff
So this one clearly does not.
You will also notice its written for SAMP (A GTA San Andreas Multiplayer MOD).
Is it just the pure ammount of traffic to the server that laggs it?
That would mean you basicly just have to generate alot of traffic to the server, no matter whats in the packets.