/explore
|
You are here 
|
devco.re | ||
| | | | |
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. | |
| | | | |
comsecuris.com
|
|
| | | | | [AI summary] This blog post discusses a detailed exploit chain targeting a mobile phone's application processor OS through a compromised modem. The author outlines the process of identifying vulnerabilities in the baseband firmware, reverse engineering the MT6795's cellular stack layers, and attempting to fuzz the MM layer for potential memory corruption issues. The post also touches on the challenges of creating a persistent rootkit via the modem and the importance of hardware isolation in securing mobile platforms. | |
| | | | |
parsiya.net
|
|
| | | | | [AI summary] The provided text is a detailed technical article discussing various methods and techniques for exploiting custom protocol handlers and command-line switches in applications. It covers topics such as UNC path injection, command-line switch abuse, remote file execution, and leveraging startup directories for persistence. The article also includes practical examples, tools like Nirsoft's URLProtocolView, and advice on how to discover and exploit vulnerabilities in applications. | |
| | | | |
jan.schnasse.org
|
|
| | | [AI summary] The page contains only technical cookie consent notices and website navigation elements without any actual article content. | ||
