Open SkillartzHD opened 5 years ago
@mikela-valve Another potential security breach that must be fixed in the Next release.
Issue seems easy to fix.
As a reference: https://github.com/dreamstalker/rehlds/pull/652
@RauliTop this is not enough
@mikela-valve This one is happening a lot too and still harming a lot of servers but there is not a real workaround unless using ReHLDS which won't fix it at all as @SkillartzHD said.
@mikela-valve This one is happening a lot too and still harming a lot of servers but there is not a real workaround unless using ReHLDS which won't fix it at all as @SkillartzHD said.
Exploit it's fixed at all in dproto and reunion. Or am I wrong?
In
NET_QueuePacket
there's thishow to access
NET_QueuePacket
with socket.sendto0xFE
= length 00xFEFF
= length 10xFEFFFF
= length 20xFEFFFFFF
= length 3 ……0xFEFFFFFFFFFFFFFF
= length 8 (max)The problem is not in that spam made by
Con_NetPrintf
, even if you remove that printf, it still comes and still creates that server side lagSolution: checking using socket.recvfrom in the server if 0xFE is then sent return