Solution against Crash

[Spik3man]

The only solution to fix the crash problem is to modify the bins.There is no other way.

 

[SIM]

The only solution to fix the crash problem is to modify the bins.There is no other way.

There's a client side fix..

 

[TriEdge]

People can crash your channels without a client too. They just need to send you the bad packet and your channel is down

 

[Drav3n]

clear
service iptables stop
IPTABLE="/sbin/iptables"


$IPTABLE -F
$IPTABLE -Z
$IPTABLE -X


#Cabal Secure Ports
#DBAgent ,GlobalMgrSvr,AuthDBAgent,RockAndRollITS,EventDBAgent
#CashDBAgent ,PCBangDBAgent,EventMgrSvr,GlobalDBAgent,PartySvr
SecPorts="32080,38190,38181,37110,38171,38180,38170,38201,38140,32001"


#Cabal Open Ports
lPort="38101" #LoginSvr Port
cPort="38121" #ChatNode Port
aPort="38151" #AgentShop Port
#WorldSvr Ports
Port1="38111"
Port2="38112"
Port3="38113"
Port4="38114"
Port5="38115"
Port6="38116"
Port7="38117"


$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp -m multiport --dports $SecPorts -j DROP
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $lPort -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $cPort -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $aPort -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port1 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port2 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port3 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port4 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port5 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port6 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port7 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
service iptables save
service iptables start

That script is not really helpful, can still crash channel using crash tool.

 

[SIM]

People can crash your channels without a client too. They just need to send you the bad packet and your channel is down

If you are talking about direct packet sending without cabalmain.exe, then I guess the iptables script above can block it.

That script is not really helpful, can still crash channel using crash tool.

Yes.. because crashtool.exe manipulate the enter channel opcode..

I have here a chatnode bad opcode that can crash worldsvr and I test it using the crashtool method of manipulating and sadly its working.. :'(

 

[124782692]

Worldsvr > baotou bytes to change it, perfect to solve collision, don't need to do other, worldsvr > bytes, this has been solved, but no one is released! Believe that will be released soon! We work together

 

[geography]

Worldsvr > baotou bytes to change it, perfect to solve collision, don't need to do other, worldsvr > bytes, this has been solved, but no one is released! Believe that will be released soon! We work together

can you share something?

 

[GODSKIN]

edit WorldSvr.bin

 

[geography]

edit WorldSvr.bin

can you give me some hex address?

 

[li198306]

MOVEAX ？ Send instructions? 0A 00
Modified to 0F 00?

 

[xender16]

This is freaking hilarious , I tested the crash tool and I stop it by enabling the SPI (stateful inspection) function of my firewall , all done the crush tool is not working... >.>.
It is funny how the whole community si working to deny some packets when you can simply add a security option to not be able to affect your network.

 

[sapeone123]

Channel is running, client side problems

 

[xender16]

my idea
iptables -A INPUT -p tcp -m tcp --tcp-flags PSH,ACK PSH,ACK -m length --length 52 -m state --state ESTABLISHED -j DROP

This idea was good if this rule wasn't blocking npc packets
I think a better solution is application layer filtering

 

[x30unlimited]

To view the content, you need to sign in or register

here's a tutorial on how to patch files in ida that's how most ppl patched the crash ur brain can't comprehend ? don't worry, practice makes perfect, just keep trying and don't give up

now stop begging to be spoon feed