i found a bug in MySql 5*, which allows me to crash any server with fp=nil.
One could probably write an exploit for this easily.
Here is what it's written in error log:
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
Cannot determine thread, fp=0xafdadb98, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html
and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8ab1bd8 = SELECT **** Removed MySql Q. doe to security.
How can i notify MySql without writing all details to exploit it publicly?