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
Inactive Support Threads
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: 770287"><p>The "The 0x00000005" error code being mentioned in that article is the Win32 error code for "Access Denied", it is converted to Win32 error code from NTSTATUS STATUS_ACCESS_DENIED (0xC0000022).</p><p></p><p>Basically since the lsass.exe process is now a protected process, handle acquisition is being denied system-wide. NtOpenProcess -> calls PsLookupProcessByProcessId to make sure the process exists -> then moves to Psp* if I remember correctly.</p><p></p><p>I'll have to check ntoskrnl.exe tomorrow and then I'll let you know the whole process of NtOpenProcess internally.</p><p></p><p>But basically the Windows kernel checks the opaque structures and see's that lsass.exe is actually set as a protected process so it blocks the operation and the caller is notified that the access to the process was denied.</p><p></p><p>Without that process handle, Mimikatz cannot access or modify the virtual memory of lsass.exe remotely unless it has an exploit to bypass the protection.</p></blockquote><p></p>
[QUOTE="Eddie Morra, post: 770287"] The "The 0x00000005" error code being mentioned in that article is the Win32 error code for "Access Denied", it is converted to Win32 error code from NTSTATUS STATUS_ACCESS_DENIED (0xC0000022). Basically since the lsass.exe process is now a protected process, handle acquisition is being denied system-wide. NtOpenProcess -> calls PsLookupProcessByProcessId to make sure the process exists -> then moves to Psp* if I remember correctly. I'll have to check ntoskrnl.exe tomorrow and then I'll let you know the whole process of NtOpenProcess internally. But basically the Windows kernel checks the opaque structures and see's that lsass.exe is actually set as a protected process so it blocks the operation and the caller is notified that the access to the process was denied. Without that process handle, Mimikatz cannot access or modify the virtual memory of lsass.exe remotely unless it has an exploit to bypass the protection. [/QUOTE]
Insert quotes…
Verification
Post reply
Top