|
You are here |
oldboy21.github.io | ||
| | | | |
disman.tl
|
|
| | | | | Developer | Hacker | Saboteur | |
| | | | |
alice.climent-pommeret.red
|
|
| | | | | ||
| | | | |
www.codeproject.com
|
|
| | | | | A detailed analysis of how to inject the .NET runtime and arbitrary .NET assemblies into unmanaged and managed processes; and how to execute managed code within those processes. | |
| | | | |
itm4n.github.io
|
|
| | | Whenever a "new" DLL hijacking / planting trick is posted on Twitter, it generates a lot of comments. "It's not a vulnerability!" or "There is a lot of hijackable DLLs on Windows..." are the most common reactions. Though, people often don't really speak about the same thing, hence the overall confusion which leads us nowhere. I don't pretend to know the ultimate truth but I felt the need to write this post in order to hopefully clarify some points. | ||