The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 198 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined property: DB_MySQLi::$google_seo_query_limit - Line: 232 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 232 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Decrement on type null has no effect, this will change in the next major version of PHP - Line: 232 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 232 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once




Just-released Minecraft exploit makes it easy to crash game servers
#1
Is MCServer vulnerable to this?
http://arstechnica.com/security/2015/04/...e-servers/
Reply
Thanks given by:
#2
This was already asked about a week ago Wink https://forum.cuberite.org/showthread.php?tid=1878

I think xoft already fixed it, but I'm not completely sure.
Reply
Thanks given by:
#3
It's not exactly fixed, it's only that MCS has been immune to that one particular piece of code; however, if someone were to modify the code just a bit (go from 300 lists to 250 lists), they could still cause slight lag on the server. The server won't run out of memory nor use extreme amounts of CPU, it will just spend a bit more time decoding packets from that particular client, and then it kicks them right afterwards, so no more parsing.

True, it could still cause problems on tight architectures such as the RasPi, those are more RAM and CPU sensitive than x86-based platforms.
Reply
Thanks given by:




Users browsing this thread: 1 Guest(s)