![]() One will be utilized as the debugger machine and the other will act as a target system. There are other options, but WinDBG is definitely the best tool for our endeavor, so l et’s get it started! WinDBG is a debugger developed by Microsoft and we will need it for debugging user and kernel space. This series will be part of my studies too, so hopefully, this will help everyone in the same situation! The Environmentįor this environment, you will need a debugger, a couple of VMs and curiosity! When you look at current CTFs for example, you will find only a few basic/introductory write-ups covering Windows protections and memory allocations, but I will try to write about the subject in future posts. Windows exploitation is certainly not an easy subject to learn since there are not many Windows challenges available. ![]() ![]() About Windows internals, I really recommend the training from Pavel Yosifovich on Pluralsight that will expand your familiarity with the system if you are new to the topic. This environment will be useful for learning Windows internals and indispensable for our future posts about its exploitation. ![]() In this blog series, I will try to set some base knowledge for Windows system debugging & exploitation and present how to setup an environment for remote kernel debugging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |