Explore >> Select a destination
|
You are here 
|
blog.acrossecurity.com | ||
| | | | |
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: | |
| | | | |
parsiya.net
|
|
| | | | | [AI summary] A security engineer explains why 'style points' like unquoted service paths or 404 injection are not real vulnerabilities and clarifies the distinction between code injection at current privilege levels versus actual privilege escalation. | |
| | | | |
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. | |
| | | | |
sam.hooke.me
|
|
| | | The home page of Sam Hooke. | ||
