How to fix this KORE Attack / Match Server Crash Attack ?

Printable View

Show 100 post(s) from this thread on one page

04-12-12
cheaterastic

How to fix this MatchServer Crash Attack by Israel

This is an update of my thread, a new way hacker can crash your MatchServer if you are using Gunz 2011.
BTW, the truth is i don't know how he do an attack, I don't know what's the name called about it, but I named it "cmd MatchServer Crash Attack" or command MatchServer Crash Attack.

This is like an /admin_halt that will crash the server. BTW, my /admin_halt already disabled/commented on the source. Whole /admin_halt codes, its conflict codes was removed from my source.

See the image below to see the matchserver logs details..
As you can see, the maximum MatchServer crash he made is 10 times in just 1 minute. At the time of 6:12 AM

I really don't know how he did it, but I believe that it is a DLL or A command to Crash the MatchServer.

Here is the Log:

Code:

[12/11/12 06:12:04] Match Server Created (Port:6000) Dueltournament Service Open(2012-12-11 Hour6, Min12) Daily Survival Ranking Request [month12 day11 hour6 min12] success to update CustomIP [12/11/12 06:12:05] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (8023, 122, 52, 121, 27, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:05] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (1524, 112, 205, 175, 146, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:06] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (2282, 58, 69, 50, 73, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:06] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7765, 117, 192, 120, 3, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:07] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (5535, 121, 96, 14, 15, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:07] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4279, 203, 87, 176, 23, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:07] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (8467, 79, 180, 203, 189, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:07] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (5762, 112, 200, 31, 171, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:08] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4818, 120, 28, 127, 221, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:08] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7544, 125, 60, 246, 141, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:09] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (8462, 117, 192, 120, 3, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:09] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4120, 118, 101, 201, 117, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:10] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (8407, 117, 192, 120, 3, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:10] MMatchDBMgr::ExceptionHandler CrashDump Entered 1 CrashDump Entered 2 Crash ( 06:12:10 ) Build Nov 30 2012 22:32:41 dwTotalMemKB = 2096584 KB dwAvailMemKB = 487040 KB dwVirtualMemKB = 2097024 KB [Exception] Address : 004dc532 ExpCode : c0000005 Flags : 00000000 #Param : 00000002 other : 00000000 [Context] GS : 00000000 FS : 0000003b ES : 00000023 DS : 00000023 EDI: 041db16c ESI: fffffffd EBX: 00000073 EDX: 0374c626 ECX: 7ffffffe EAX: 53727245 EBP: 041daee4 EIP: 004dc532 CS : 0000001b Flg: 00010202 ESP: 041dae58 SS : 00000023 [Stack] 036f55b0 00561810 00000001 0018c2a0 041daf48 7c829dad 00161378 00000007 00000000 7c829c87 00000000 00000000 00000000 00000000 00000000 00000000 00000057 00000003 53727245 ffffffff 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 041daf00 00006a34 041dac64 00000000 041db070 7c8280e0 7c82c3a0 ffffffff 7c82c399 7c82c4dd 00000001 041daf24 041dafac 00160000 00000000 7ffd8c00 00000228 00000045 000149ff 041dae78 40100080 041db070 7c8280e0 7c829dd0 ffffffff 00000000 7c829c87 041dafc4 77e64a53 000000b7 ffffffff 00000003 00000080 00000018 00000000 041dafac 00000042 00000000 041daf90 00000000 00000000 00000000 00000000 0000000c 00000002 7c810101 7ffd8c00 000000e4 00000000 00000001 021a00ec 0018c2a8 00000003 00000000 0018c2a8 00000003 041dafe8 77e41a8e 00000424 7c827599 77e6b3fb 00000424 041daff0 041daff8 00000008 00000004 ffffffff 00000000 ffffffff 00000003 00000424 004e4ff3 00000003 00000424 00529639 00000002 00000000 0000000c 00000000 00000001 40000000 00000004 00000002 00000000 00529639 041db080 004e53a2 014a1fa0 004e5108 00000003 004e50f9 00529639 00000002 CrashDump Leaving CrashDump Leaved

I NEED HELP, now, HOW TO FIX THIS? NO ONE RELEASED ANY ANTI for this problem.

I AM USING Modified Source (CTF + Anti-Lead + DamageCounter + Fixes), so other people using this, if your server will grow, some people will attack yours.

Another problem: His Character name is NONAME or full of spacebar chars, 12 spacebar, also he made a Character Name ^2Isr aelatk which will be output on Gunz InGame as Isr aelatk, this is really a DLL hack.

MATCH SERVER LOGS:
http://www.mediafire.com/conv/1fdea5...346d64976g.jpg

I am done, I have applied the LogDB database on my SQL Server.
Now these are the problems encountered on MatchLog.txt

I am so sorry, I really don't know how to fix this bug even though I keep reading its each lines.

Code:

[12/12/12 04:16:16] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 13595, 161, 1, 2, 39644, 1738)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:16:28] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(808895118, 11713, 150, 8, 0, 227392, 9984)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:16:32] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 14416, 91, 0, 3, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:16:35] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 12901, 3739007, 0, 0, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:16:59] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(2560, 14354, 396, 4, 9, 87550, 3904)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:01] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(808887424, 14054, 115, 5, 1, 126973, 5398)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:01] MMatchDBMgr::ExceptionHandler - Disconnect [12/12/12 04:17:01] MMatchDBMgr::ExceptionHandler - Reconnect [12/12/12 04:17:01] MMatchDBMgr::ExceptionHandler - This(38665688) [12/12/12 04:17:15] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 8476, 442, 13, 10, 428145, 18800)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:15] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(808887424, 8350, 29, 0, 0, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:17] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(2560, 5434, 142, 3, 2, 74018, 3174)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:17] MMatchDBMgr::ExceptionHandler - Disconnect [12/12/12 04:17:17] MMatchDBMgr::ExceptionHandler - Reconnect [12/12/12 04:17:17] MMatchDBMgr::ExceptionHandler - This(40762840) [12/12/12 04:17:20] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 12285, 140, 2, 2, 84422, 3500)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:30] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(2560, 5434, 155, 3, 2, 74018, 3174)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:33] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 2118, 875, 24, 21, 769114, 33771)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:33] MMatchDBMgr::ExceptionHandler - Disconnect [12/12/12 04:17:33] MMatchDBMgr::ExceptionHandler - Reconnect [12/12/12 04:17:33] MMatchDBMgr::ExceptionHandler - This(41942488) [12/12/12 04:17:38] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(808895230, 5434, 163, 3, 2, 74018, 3174)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:41] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(808895230, 12840, 334, 0, 4, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:41] MMatchDBMgr::ExceptionHandler - Disconnect [12/12/12 04:17:41] MMatchDBMgr::ExceptionHandler - Reconnect [12/12/12 04:17:41] MMatchDBMgr::ExceptionHandler - This(37617112) [12/12/12 04:17:43] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 8331, 45, 0, 2, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:51] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 13276, 533, 15, 13, 558229, 23936)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:17:53] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 14100, 33, 1, 1, 28220, 1256)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:18:02] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 14100, 42, 1, 1, 28220, 1256)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:18:02] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(2560, 14073, 940, 11, 23, 334662, 14690)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:18:04] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 5434, 21, 0, 1, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:18:09] GARBAGE SESSION CLEANING : m_This(02), ClientCount=68, SessionCount=69, AgentCount=1, CommandPool=153, objHistoryCount=100 [12/12/12 04:18:58] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 5434, 24, 0, 1, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:18:58] MMatchDBMgr::ExceptionHandler - Disconnect [12/12/12 04:18:58] MMatchDBMgr::ExceptionHandler - Reconnect [12/12/12 04:18:58] MMatchDBMgr::ExceptionHandler - This(39714264) [12/12/12 04:19:03] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 5434, 29, 0, 1, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:19:05] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 4096, 10, 0, 0, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:19:06] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(2560, 5434, 32, 0, 1, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:19:10] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(2560, 13372, 280, 7, 3, 191641, 8168)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:19:16] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(808887424, 14110, 335, 1, 9, 25619, 1126)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:19:32] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(648, 14150, 176, 0, 0, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:19:45] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(2560, 3737, 228, 6, 12, 174539, 7311)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:19:52] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 13372, 322, 7, 3, 191641, 8168)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:19:59] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 12901, 62, 0, 2, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:20:08] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 9322, 819, 12, 17, 388484, 17054)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:20:33] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(40502, 12512, 431, 17, 11, 643620, 28055)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:20:39] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 4096, 16, 0, 0, 0, 0)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/12/12 04:20:50] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(360, 6966, 64, 2, 1, 114644, 3819)} ), ErrCode( -1 ) ErrMsg - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_GamePlayerLog_ID". The conflict occurred in database "LogDB", table "dbo.GameLog", column 'ID'. The statement has been terminated. State:23000,Native:547,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] State:01000,Native:3621,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]

---------------------------------------------
Old thread description:

Spoiler:

I am using Modified Source (CTF + Anti-Lead + DamageCounter + Fixes)

HERE IS THE LOG:

(oldLOG, might be useless)

Spoiler:

Code:

[12/03/12 11:44:55] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spChangeGambleItemToRewardNormalItem (5296, 212709, 1000004, 74, 22507, 168)} ), ErrCode( -1 ) ErrMsg - Could not find stored procedure 'spChangeGambleItemToRewardNormalItem'. State:37000,Native:2812,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/03/12 11:45:32] MMatchDBMgr::ExceptionHandler CrashDump Entered 1 CrashDump Entered 2 Crash ( 11:45:32 ) Build Nov 30 2012 22:32:41 dwTotalMemKB = 2096584 KB dwAvailMemKB = 582520 KB dwVirtualMemKB = 2097024 KB [Exception] Address : 004dcb92 ExpCode : c0000005 Flags : 00000000 #Param : 00000002 other : 00000000 [Context] GS : 00000000 FS : 0000003b ES : 00000023 DS : 00000023 EDI: 026db16c ESI: fffffffd EBX: 00000073 EDX: 037ee00e ECX: 7ffffffe EAX: 53727245 EBP: 026daee4 EIP: 004dcb92 CS : 0000001b Flg: 00010202 ESP: 026dae58 SS : 00000023 [Stack] 03824a00 00562810 00000001 00162168 026daf48 7c829dad 00161378 00000007 00000000 7c829c87 00000000 00000000 00000000 00000000 00000000 00000000 00000057 00000003 53727245 ffffffff 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 026daf00 00005e4c 026dac64 00000000 026db070 7c8280e0 7c82c3a0 ffffffff 7c82c399 7c82c4dd 00000001 026daf24 026dafac 00160000 00000000 7ffdac00 00000228 00000045 000149ff 026dae78 40100080 026db070 7c8280e0 7c829dd0 ffffffff 00000000 7c829c87 026dafc4 77e64a53 000000b7 ffffffff 00000003 00000080 00000018 00000000 026dafac 00000042 00000000 026daf90 00000000 00000000 00000000 00000000 0000000c 00000002 7c810101 7ffdac00 000000e4 00000000 00000001 021a00ec 00162170 00000003 00000000 00162170 00000003 026dafe8 77e41a8e 00000438 7c827599 77e6b3fb 00000438 026daff0 026daff8 00000008 00000004 ffffffff 00000000 ffffffff 00000003 00000438 004e5653 00000003 00000438 0052a639 00000002 00000000 0000000c 00000000 00000001 40000000 00000004 00000002 00000000 0052a639 026db080 004e5a02 014a1fa0 004e5768 00000003 004e5759 0052a639 00000002 CrashDump Leaving CrashDump Leaved

My Last MatchLog crashed 7:25 PM 12/5/2012 (by an attacker / multiple crashing): (dark red = caused by crash & red lines = crash)

Code:

[12/04/12 07:58:11] Match Server Created (Port:6000) Dueltournament Service Open(2012-12-4 Hour7, Min58) Daily Survival Ranking Request [month12 day4 hour7 min58] success to update CustomIP [12/04/12 07:58:12] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7985, 79, 180, 203, 189, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:12] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4642, 121, 54, 58, 143, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:12] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (5797, 121, 54, 32, 140, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:13] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (2764, 49, 145, 3, 115, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:14] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4279, 203, 87, 176, 23, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:15] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (5479, 180, 190, 231, 192, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:15] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7929, 119, 92, 243, 34, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:16] MMatchDBMgr::ExceptionHandler CrashDump Entered 1 CrashDump Entered 2 Crash ( 07:58:16 ) Build Nov 30 2012 22:32:41 dwTotalMemKB = 2096584 KB dwAvailMemKB = 635200 KB dwVirtualMemKB = 2097024 KB [Exception] Address : 004dcb92 ExpCode : c0000005 Flags : 00000000 #Param : 00000002 other : 00000000 [Context] GS : 00000000 FS : 0000003b ES : 00000023 DS : 00000023 EDI: 024db16c ESI: fffffffd EBX: 00000073 EDX: 0371ed36 ECX: 7ffffffe EAX: 53727245 EBP: 024daee4 EIP: 004dcb92 CS : 0000001b Flg: 00010202 ESP: 024dae58 SS : 00000023 [Stack] 0371e998 00562810 00000001 0018c2a0 024daf48 7c829dad 00161378 00000007 00000000 7c829c87 00000000 00000000 00000000 00000000 00000000 00000000 00000057 00000003 53727245 ffffffff 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 024daf00 00000c5c 024dac64 00000000 024db070 7c8280e0 7c82c3a0 ffffffff 7c82c399 7c82c4dd 00000001 024daf24 024dafac 00160000 00000000 7ffdcc00 00000228 00000045 000149ff 024dae78 40100080 024db070 7c8280e0 7c829dd0 ffffffff 00000000 7c829c87 024dafc4 77e64a53 000000b7 ffffffff 00000003 00000080 00000018 00000000 024dafac 00000042 00000000 024daf90 00000000 00000000 00000000 00000000 0000000c 00000002 7c810101 7ffdcc00 000000e2 00000000 00000001 021a00ea 0018c2a8 00000003 00000000 0018c2a8 00000003 024dafe8 77e41a8e 000003f8 7c827599 77e6b3fb 000003f8 024daff0 024daff8 00000008 00000004 ffffffff 00000000 ffffffff 00000003 000003f8 004e5653 00000003 000003f8 0052a639 00000002 00000000 0000000c 00000000 00000001 40000000 00000004 00000002 00000000 0052a639 024db080 004e5a02 014a1fa0 004e5768 00000003 004e5759 0052a639 00000002 CrashDump Leaving CrashDump Leaved

PLEASE HELP!

ADVANCE THANKS TO THOSE WHO CAN HELP.. By the way, on Gregon13's new released, it has suggest Korea Match Server Crash.
So please help, the more you help, the more you help others, because I am using Gregon13's source, and if you'd help me, it will be useful for others because Gregon13's new released is very useful of all releases.
04-12-12
OldSchoolGZ

Re: How to fix this KORE Attack / Match Server Crash Attack ?

your using a bad DB your server can't find certain procs
04-12-12
cheaterastic

Re: How to fix this KORE Attack / Match Server Crash Attack ?

Quote:

Originally Posted by OldSchoolGZ

your using a bad DB your server can't find certain procs

OMG! I really don't know if my Database is bad.

There is an hacker named: no name or his name is 12 space.
He do a MatchServer attack, and I think there is no wrong with my DB...
- - If ever he came, he warn my player and to crash my server.

I really need some guide to fix my Match Server Crash by an Hacker. It's a Kore Attack I think.

BTW, thanks for reply.
04-12-12
OldSchoolGZ

Re: How to fix this KORE Attack / Match Server Crash Attack ?

which files are used for this and according to your log your missin a proc as far as i'm aware kore doesn't work on 1.5 I may be wrong or it may be an exploit found in the source
04-12-12
xTrafx

Re: How to fix this KORE Attack / Match Server Crash Attack ?

Quote:

Originally Posted by OldSchoolGZ

which files are used for this and according to your log your missin a proc as far as i'm aware kore doesn't work on 1.5 I may be wrong or it may be an exploit found in the source

agree kore was release to attack 2007 or 2008 client server if i remember.
04-12-12
cheaterastic

Re: How to fix this KORE Attack / Match Server Crash Attack ?

Quote:

Originally Posted by OldSchoolGZ

which files are used for this and according to your log your missin a proc as far as i'm aware kore doesn't work on 1.5 I may be wrong or it may be an exploit found in the source

The attacker from my Server had downloaded my Client. And he played on my server using a 'no name' character which had 12 space (spacebar). He inject a DLL to my Gunz.exe i think just to get that name
Another one, he warned my Players that he will Crash my Server, and yes, it's true, my server crashed, 2 times in 2 days, and today, I believe that it's a MatchServer attack, because I see my MatchServer crashed multiple times in just 5 seconds.

This what you mean on Bad DB. These are the ErrSQL from MatchLog, but this doesn't matter because this ErrSQL already occured multiple times and my MatchServer doesn't crash. My MatchServer crashed only from an Attack. And I think it's a Kore Attack or Match Server Crash Attack.

Code:

[12/03/12 07:14:31] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7338, 112, 209, 130, 38, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/03/12 07:14:52] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertGameLog2 (11906, 'Town', 'Death Match(Team)')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.GameLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/03/12 07:15:25] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL InsertGamePlayerLog(3568, 4850, 2971384, 0, 0, 0, 0)} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.GamePlayerLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]

I really don't know if It's a KORE attack or Database side that's why the attacker was able to crash.
04-12-12
OldSchoolGZ

Re: How to fix this KORE Attack / Match Server Crash Attack ?

he's exploiting the source and crashing it through a custom dll then or a home made program designed to attack the exploits and cause a crash I'll look into it but can't guarantee anything
04-12-12
GzFKoron

Re: How to fix this KORE Attack / Match Server Crash Attack ?

I highly doubt he is, most people who download hacks to use create the illusion that they are pro hackers and can completely ruin anything just by using threats, in this case he is probably aware that your server crashes due to the database problems and is making it seem like he is the one doing it.
04-12-12
cheaterastic

Re: How to fix this KORE Attack / Match Server Crash Attack ?

Gregon13/OldSchoolGZ, could you give me the correct database, I will just script it...
Maybe the spChangeGambleItemToRewardNormalItem...
The last log before the ERROR LOG of Crash is

Code:

[12/03/12 11:44:55] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spChangeGambleItemToRewardNormalItem (5296, 212709, 1000004, 74, 22507, 168)} ), ErrCode( -1 ) ErrMsg - Could not find stored procedure 'spChangeGambleItemToRewardNormalItem'. State:37000,Native:2812,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]

But this Log have already occurred multiple times. But maybe, because of Gamble item, he is able to CRASH my SERVER. But it is so misleading because he have crash my server 7 times in just 5 seconds, yesterday.

Quote:

Originally Posted by OldSchoolGZ

he's exploiting the source and crashing it through a custom dll then or a home made program designed to attack the exploits and cause a crash I'll look into it but can't guarantee anything

YEAH Gregon13. I think so.
1 more thing, he can chat with bad words, that are already placed in my abuse.txt and he pretended that he can't chat because we've saw . Maybe he got my encrypted keys or still such a DLL. I really don't know if it's a MatchServer Crash Attack or KORE attack. Last time, when I had Gunz 2008 server, I have an anti-kore, but it was so failed because it is limited to 32 players and so yuck because I sold it.

Quote:

Originally Posted by SheenUK

I highly doubt he is, most people who download hacks to use create the illusion that they are pro hackers and can completely ruin anything just by using threats, in this case he is probably aware that your server crashes due to the database problems and is making it seem like he is the one doing it.

Yea. But maybe it's a real KORE/MatchServer-Crash Attack, because 1 times, he did a multiple crashing of my MatchServer in just 5 seconds (7 times crashed).
04-12-12
Vusion

Re: How to fix this KORE Attack / Match Server Crash Attack ?

There's no kore involved with this crash.....

MMatchDBMgr::ExceptionHandler
MMATCHDATABASEMANAGER.::EXCEPTIONHANDLER.

It's self explanatory why it's crashing.

Code:

CREATE PROC dbo.spChangeGambleItemToRewardNormalItem @CID INT , @CIID INT , @GIID INT , @GRIID INT , @RewardItemID INT , @RewardRentPeriod INT AS BEGIN SET NOCOUNT ON; ----------------------------------------------------------------------------- DECLARE @NowDate DATETIME; SET @NowDate = GETDATE(); DECLARE @GambleItemCount INT; SELECT @GambleItemCount = ISNULL(Cnt, 1) FROM CharacterItem(NOLOCK) WHERE CIID = @CIID AND CID IS NOT NULL; ----------------------------------------------------------------------------- SET XACT_ABORT ON; BEGIN TRAN ----------- ---------------------------------------------------------------------------------------- IF( @GambleItemCount > 1 ) BEGIN UPDATE CharacterItem SET Cnt = Cnt - 1 WHERE CID = @CID AND CIID = @CIID END ELSE BEGIN DELETE CharacterItem WHERE CID = @CID AND CIID = @CIID END --------------------------------------------------------------------------------------- INSERT CharacterItem(CID, ItemID, RegDate, RentDate, RentHourPeriod, Cnt) VALUES (@CID, @RewardItemID, @NowDate, @NowDate, @RewardRentPeriod, 1) DECLARE @OrderCIID INT; SET @OrderCIID = @@IDENTITY; COMMIT TRAN ----------- SET XACT_ABORT OFF; INSERT dbo.ItemChangeLog_CharacterItem(ChangeType, ChangeDate, CID, CIID, ItemID, [Count]) VALUES (202, @NowDate, @CID, @CIID, @GIID, 1); INSERT dbo.ItemChangeLog_CharacterItem(ChangeType, ChangeDate, CID, CIID, ItemID, [Count]) VALUES (102, @NowDate, @CID, @OrderCIID, @RewardItemID, 1); INSERT INTO LogDB..GambleLog(CID, GIID, RewardItemID, RegDate, RentHourPeriod, ItemCnt) VALUES (@CID, @GIID, @RewardItemID, @NowDate, @RewardRentPeriod, 1); ---------------------------------------------------------------------------------------- SELECT @OrderCIID AS 'ORDERCIID' END GO
05-12-12
cheaterastic

Re: How to fix this KORE Attack / Match Server Crash Attack ?

Quote:

Originally Posted by Vusion

There's no kore involved with this crash.....

MMatchDBMgr::ExceptionHandler
MMATCHDATABASEMANAGER.::EXCEPTIONHANDLER.

It's self explanatory why it's crashing.

Spoiler:

Code:

CREATE PROC dbo.spChangeGambleItemToRewardNormalItem @CID INT , @CIID INT , @GIID INT , @GRIID INT , @RewardItemID INT , @RewardRentPeriod INT AS BEGIN SET NOCOUNT ON; ----------------------------------------------------------------------------- DECLARE @NowDate DATETIME; SET @NowDate = GETDATE(); DECLARE @GambleItemCount INT; SELECT @GambleItemCount = ISNULL(Cnt, 1) FROM CharacterItem(NOLOCK) WHERE CIID = @CIID AND CID IS NOT NULL; ----------------------------------------------------------------------------- SET XACT_ABORT ON; BEGIN TRAN ----------- ---------------------------------------------------------------------------------------- IF( @GambleItemCount > 1 ) BEGIN UPDATE CharacterItem SET Cnt = Cnt - 1 WHERE CID = @CID AND CIID = @CIID END ELSE BEGIN DELETE CharacterItem WHERE CID = @CID AND CIID = @CIID END --------------------------------------------------------------------------------------- INSERT CharacterItem(CID, ItemID, RegDate, RentDate, RentHourPeriod, Cnt) VALUES (@CID, @RewardItemID, @NowDate, @NowDate, @RewardRentPeriod, 1) DECLARE @OrderCIID INT; SET @OrderCIID = @@IDENTITY; COMMIT TRAN ----------- SET XACT_ABORT OFF; INSERT dbo.ItemChangeLog_CharacterItem(ChangeType, ChangeDate, CID, CIID, ItemID, [Count]) VALUES (202, @NowDate, @CID, @CIID, @GIID, 1); INSERT dbo.ItemChangeLog_CharacterItem(ChangeType, ChangeDate, CID, CIID, ItemID, [Count]) VALUES (102, @NowDate, @CID, @OrderCIID, @RewardItemID, 1); INSERT INTO LogDB..GambleLog(CID, GIID, RewardItemID, RegDate, RentHourPeriod, ItemCnt) VALUES (@CID, @GIID, @RewardItemID, @NowDate, @RewardRentPeriod, 1); ---------------------------------------------------------------------------------------- SELECT @OrderCIID AS 'ORDERCIID' END GO

Hm.. Yes, I've already executed that SQL query, since the day of this thread (after its 5 hrs), I keep searching the GambleReward ErrSQL from my MatchLog to Google.com. But today, I saw my MatchServer, still got crashed 9 times (10 seconds on every crashed)..

But then, I will try to execute again that SQLquery, Vusion, maybe they have difference... Thanks for reply.

> spChangeGambleItemToRewardNormalItem deleted (from Programmability > Stored Procedures), and now SQLquery executed.
> > Command(s) completed successfully.

BTW, this is My Last MatchLog crashed: (dark red = caused by crash & red lines = crash)

Code:

[12/04/12 07:58:11] Match Server Created (Port:6000) Dueltournament Service Open(2012-12-4 Hour7, Min58) Daily Survival Ranking Request [month12 day4 hour7 min58] success to update CustomIP [12/04/12 07:58:12] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7985, 79, 180, 203, 189, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:12] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4642, 121, 54, 58, 143, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:12] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (5797, 121, 54, 32, 140, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:13] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (2764, 49, 145, 3, 115, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:14] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4279, 203, 87, 176, 23, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:15] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (5479, 180, 190, 231, 192, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:15] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7929, 119, 92, 243, 34, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/04/12 07:58:16] MMatchDBMgr::ExceptionHandler CrashDump Entered 1 CrashDump Entered 2 Crash ( 07:58:16 ) Build Nov 30 2012 22:32:41 dwTotalMemKB = 2096584 KB dwAvailMemKB = 635200 KB dwVirtualMemKB = 2097024 KB [Exception] Address : 004dcb92 ExpCode : c0000005 Flags : 00000000 #Param : 00000002 other : 00000000 [Context] GS : 00000000 FS : 0000003b ES : 00000023 DS : 00000023 EDI: 024db16c ESI: fffffffd EBX: 00000073 EDX: 0371ed36 ECX: 7ffffffe EAX: 53727245 EBP: 024daee4 EIP: 004dcb92 CS : 0000001b Flg: 00010202 ESP: 024dae58 SS : 00000023 [Stack] 0371e998 00562810 00000001 0018c2a0 024daf48 7c829dad 00161378 00000007 00000000 7c829c87 00000000 00000000 00000000 00000000 00000000 00000000 00000057 00000003 53727245 ffffffff 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 024daf00 00000c5c 024dac64 00000000 024db070 7c8280e0 7c82c3a0 ffffffff 7c82c399 7c82c4dd 00000001 024daf24 024dafac 00160000 00000000 7ffdcc00 00000228 00000045 000149ff 024dae78 40100080 024db070 7c8280e0 7c829dd0 ffffffff 00000000 7c829c87 024dafc4 77e64a53 000000b7 ffffffff 00000003 00000080 00000018 00000000 024dafac 00000042 00000000 024daf90 00000000 00000000 00000000 00000000 0000000c 00000002 7c810101 7ffdcc00 000000e2 00000000 00000001 021a00ea 0018c2a8 00000003 00000000 0018c2a8 00000003 024dafe8 77e41a8e 000003f8 7c827599 77e6b3fb 000003f8 024daff0 024daff8 00000008 00000004 ffffffff 00000000 ffffffff 00000003 000003f8 004e5653 00000003 000003f8 0052a639 00000002 00000000 0000000c 00000000 00000001 40000000 00000004 00000002 00000000 0052a639 024db080 004e5a02 014a1fa0 004e5768 00000003 004e5759 0052a639 00000002 CrashDump Leaving CrashDump Leaved

I will reply again to this thread, if my MatchServer crash again by an attacker.
05-12-12
Vusion

Re: How to fix this KORE Attack / Match Server Crash Attack ?

Comment out the insert query in the stored procedure spInsertConnLog.

Too lazy to upload LogDB..
05-12-12
OldSchoolGZ

Re: How to fix this KORE Attack / Match Server Crash Attack ?

you need the 1.5 database files make sure to add LogDB I don't get proc errors with my files you shouldn't either
11-12-12
cheaterastic

Re: How to fix this KORE Attack / Match Server Crash Attack ?

Please help, now I see that he made a Name hack, he made a charactername: ^2Isr aelatk which will outputted at Isr aelatk on the Gunz Ingame.

Now, he have attacked 10 times in 1 minute, so I think it is a command or a DLL hack.

My New MatchLog:

Code:

[12/11/12 06:12:04] Match Server Created (Port:6000) Dueltournament Service Open(2012-12-11 Hour6, Min12) Daily Survival Ranking Request [month12 day11 hour6 min12] success to update CustomIP [12/11/12 06:12:05] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (8023, 122, 52, 121, 27, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:05] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (1524, 112, 205, 175, 146, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:06] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (2282, 58, 69, 50, 73, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:06] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7765, 117, 192, 120, 3, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:07] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (5535, 121, 96, 14, 15, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:07] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4279, 203, 87, 176, 23, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:07] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (8467, 79, 180, 203, 189, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:07] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (5762, 112, 200, 31, 171, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:08] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4818, 120, 28, 127, 221, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:08] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (7544, 125, 60, 246, 141, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:09] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (8462, 117, 192, 120, 3, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:09] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (4120, 118, 101, 201, 117, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:10] MMatchDBMgr::ExceptionHandler ErrSQL( {CALL spInsertConnLog (8407, 117, 192, 120, 3, '')} ), ErrCode( -1 ) ErrMsg - Invalid object name 'LogDB.dbo.ConnLog'. State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [12/11/12 06:12:10] MMatchDBMgr::ExceptionHandler CrashDump Entered 1 CrashDump Entered 2 Crash ( 06:12:10 ) Build Nov 30 2012 22:32:41 dwTotalMemKB = 2096584 KB dwAvailMemKB = 487040 KB dwVirtualMemKB = 2097024 KB [Exception] Address : 004dc532 ExpCode : c0000005 Flags : 00000000 #Param : 00000002 other : 00000000 [Context] GS : 00000000 FS : 0000003b ES : 00000023 DS : 00000023 EDI: 041db16c ESI: fffffffd EBX: 00000073 EDX: 0374c626 ECX: 7ffffffe EAX: 53727245 EBP: 041daee4 EIP: 004dc532 CS : 0000001b Flg: 00010202 ESP: 041dae58 SS : 00000023 [Stack] 036f55b0 00561810 00000001 0018c2a0 041daf48 7c829dad 00161378 00000007 00000000 7c829c87 00000000 00000000 00000000 00000000 00000000 00000000 00000057 00000003 53727245 ffffffff 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 041daf00 00006a34 041dac64 00000000 041db070 7c8280e0 7c82c3a0 ffffffff 7c82c399 7c82c4dd 00000001 041daf24 041dafac 00160000 00000000 7ffd8c00 00000228 00000045 000149ff 041dae78 40100080 041db070 7c8280e0 7c829dd0 ffffffff 00000000 7c829c87 041dafc4 77e64a53 000000b7 ffffffff 00000003 00000080 00000018 00000000 041dafac 00000042 00000000 041daf90 00000000 00000000 00000000 00000000 0000000c 00000002 7c810101 7ffd8c00 000000e4 00000000 00000001 021a00ec 0018c2a8 00000003 00000000 0018c2a8 00000003 041dafe8 77e41a8e 00000424 7c827599 77e6b3fb 00000424 041daff0 041daff8 00000008 00000004 ffffffff 00000000 ffffffff 00000003 00000424 004e4ff3 00000003 00000424 00529639 00000002 00000000 0000000c 00000000 00000001 40000000 00000004 00000002 00000000 00529639 041db080 004e53a2 014a1fa0 004e5108 00000003 004e50f9 00529639 00000002 CrashDump Leaving CrashDump Leaved
11-12-12
Solaire

Re: How to fix this KORE Attack / Match Server Crash Attack ?

Quote:

Originally Posted by Vusion

Comment out the insert query in the stored procedure spInsertConnLog.

Too lazy to upload LogDB..

The exception handler doesn't crash the MatchServer, the server just crashed before the full error message was flushed to the log file.

On-topic:
Get a programmer to work with you on your server, there's plenty of this exploits, I could name at least 20 functions from the top of my head that does this shit. Not going to bother with people that don't even know they can load .dmp files in Visual Studio and find out why it crashed with one mouse click.

Show 100 post(s) from this thread on one page