Explore >> Select a destination
|
You are here 
|
pentestlab.blog | ||
| | | | |
macrosec.tech
|
|
| | | | | The first thing we need to do is to identify which dll is crucial for discord to run because that is the dll we will use to perform dll hijacking. In order to find out, we need to open the file location of discord and we see: To identify the COM Keys of Chrome that we can use for COM Hijacking, we use the tool Process Monitor to identify all the processes running when Chrome runs, we also discover the COM servers that are missing CLSID's and the ones which don't require elevated privileges. We use the following filters: | |
| | | | |
www.codecentric.de
|
|
| | | | | Relative Path DLL Hijacking: Leverage legitimate Windows programs as a Red Teamer to run your own code. | |
| | | | |
whatdoiknowjr.com
|
|
| | | | | 1 post published by Jared Rascher on June 19, 2024 | |
| | | | |
oldboy21.github.io
|
|
| | | Reflective DLL After some time spent on implementing a Reflective DLL and its beloved Loader/Injector I thought that it could have been a very great first topic for what it might become a long-ish series of blog posts about security, but mostly struggles and C(++). First reason is that I felt like I was struggling a bit finding resources that would really take the topic as a whole and explain any single step, and the reasoning behind it. | ||
