Tracing SQL Queries in Real Time for MySQL Databases using WinDbg and Basic Assembler Knowledge

https://www.codeproject.com/Articles/43305/Tracing-SQL-Queries-in-Real-Time-for-MySQL-Databas

 

 

Assembly and MySQL

Introduction

One of the more interesting things for any person is to see how the internal engines from the server software work. The purpose of this article is to show how we can apply basic assembler knowledge to find interesting runtime information.

Few days ago, my friend was involved on PHP+MYSQL site development. He was experiencing some issues.

Ok, we can start.

1. You will need MySQL installation download and install any version of MySQL. Please make sure that your MySQLD service is running successfully (In other words, ensure that your MySQL is working properly).
2. Download the latest version of Windbg for Windows from the Microsoft site.
3. Launch Windbg.
4. Press F6 and attach the mysqld.exe process.
5. Set the Windbg symbols properly by using File->Symbols File Path:srv*c:\windows*http://msdl.microsoft.com/download/symbols.
6. On Windbg command line, execute .reload.
7. Press F5 to run the process (When you attach the process, this gets frozen). Using F5 or with G command, the process runs.
8. Here is the tricky part. MYSQLD.exe process (or service in this case) is in charge of executing the SQL Queries from PHP pages, or MYSQL different clients. Navicat is a cool MYSQL client which allows us to see the MYSQL Server in a graphical mode, like Microsoft Management Studio does with SQL Server.
9. Let's start navicat tool for educative purposes (if you want), or use your own PHP or any other application which is a MYSQL Client.
10. EXECUTE is the magic word. The tricky part is: Why if MYSQLD.EXE process performs a SQL Query executing any kind of EXECUTE function on any part of their internal code? Let's put a breakpoint there.
11. Breakpoint: Stop the current MYSQLD Execution by CTRL+Break on Windbg and put the following command: bm *mysqld*!*execute* (BM=break on mask, library all *mysqld* and function *execute*).
12. Press F5 and perform any client operation with PHP Page or Navicat or any other MYSQL client.
13. You will see a freeze in your page or navicat: Why? Because MYSQLD was stopped. Lets see the windbg.

    

14. Nice, the MYSQLD process stopped on MYSQLD!MYSQL_EXECUTE_COMMAND, let's see the Stack Trace: Use KB command:
15. As you can see, you can observe directly the input parameters for MYSQL_EXECUTE_COMMAND on Args to Child section. Every hexadecimal value there represents normally a pointer to any specified data structure. Is any string there on any of the Args to Child pointer? Let's examine this.
16. Click on View->Memory. On Address, write the Pointer (captured from Args to child) try with 01eb2630 and the other args to child:

    

17. We did not see any interesting thing on all args to child parameters for MYSQL_EXECUTE_COMMAND, but what about the previous function: mysql_parse?

    

18. Eureka! There is something interesting there. What if we print the value there? Let's execute: .printf “%ma”.03b62a68:

    

19. Yes, this is definitely a SQL Query captured from MYSQLD process. Now when we have the function that we want, delete all breakpoints by using the command BC * and use bp mysqld!mysql_parse and continue the execution by using F5 or G windbg command line.
20. Now our windbg stopped on mysqld!mysql_parse.
21. The one million question is: everytime that any MYSQL Query executes something, it will freeze my app until press F5 app? The answer is no, if we use a more intelligent breakpoint. We know the functionmysql_parse, but in which memory address it is stored? This is a call stack theory:

    

22. Let's explain this, when the process is starting a function, it pushes the Function parameters to be used. Then what happens with ESP processor register? Example: VOID SUM(INT X,INT *Y). ESP represents theTOP of the stack, and EBP the base address for the Stack. Let's assume that ESP=1000.
1. The process pushes the pointer to the Y value and ESP decreases their value, decreases the top of the stack? Sounds confusing, Yes it's true, in the Windows operative system, the TOP of the stack is in the lower part of memory than EBP (Base pointer of the stack) ESP=ESP-4 : 996.
2. The process pushes the value of X ESP=ESP-4 : 992.
3. The process push the return address for the previous function: ESP=ESP-4 : 998.
23. When the Windbg stops, the stack is in the c state. For example, you can find the second parameter by just executing a simple math operation: 2º parameter is located in the POI(ESP+8), as we can see the Windbg previous picture, YES, our string is the second parameter. Let's try this:
24. Printing the 2º parameter: .printf “%ma”,poi(esp+8).

    

25. Why POI? Poi in windbg represents or gets the pointer address of ESP+8, %ma means or represent just a ASCII chars. %mu represents Unicode.
26. Good, now we can put together in a simple breakpoint.
27. The complete breakpoint: bp mysqld!mysql_parse ".printf \"\\n%ma\",poi(esp+8);gc"
28. When we set Bp=breakpoint in the function mysqld!mysql_parse, it prints an ASCII string given a pointer to the esp+8 (second parameter, and gc to continue the execution without stop.

 

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)