Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
General Security Discussions
Hiding malware in Windows – The basics of code injection
Message
<blockquote data-quote="Eddie Morra" data-source="post: 770169"><p>If you're using SRP like AppGuard then you have features like memory protection which can be useful but SUA won't be handy for things like preventing RCE into processes like explorer.exe because explorer.exe is standard rights. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>SUA will only really help in terms of preventing code injection if the launcher isn't allowed to run as admin (e.g. you don't go through the UAC prompt so it either refuses to run or runs as standard rights) but wants to target an elevated process. In that case, the process handle acquisition will be refused by the Windows kernel due to integrity level of the caller and the target.</p><p></p><p>The way it works is you cannot open a handle to a process at a higher integrity as you. You'd have to somehow escalate your privileges officially (e.g. through UAC procedure) or with an privilege escalation exploit.</p></blockquote><p></p>
[QUOTE="Eddie Morra, post: 770169"] If you're using SRP like AppGuard then you have features like memory protection which can be useful but SUA won't be handy for things like preventing RCE into processes like explorer.exe because explorer.exe is standard rights. :) SUA will only really help in terms of preventing code injection if the launcher isn't allowed to run as admin (e.g. you don't go through the UAC prompt so it either refuses to run or runs as standard rights) but wants to target an elevated process. In that case, the process handle acquisition will be refused by the Windows kernel due to integrity level of the caller and the target. The way it works is you cannot open a handle to a process at a higher integrity as you. You'd have to somehow escalate your privileges officially (e.g. through UAC procedure) or with an privilege escalation exploit. [/QUOTE]
Insert quotes…
Verification
Post reply
Top