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
Protecting processes from injection via SetWindowsHookEx() ?
Message
<blockquote data-quote="Deleted member 65228" data-source="post: 730814"><p>Well, if you're loading an unsigned device driver, the last thing you want is for a BSOD to be triggered if the system recognizes there's an unsigned device driver loaded. Bypassing Driver Signature Enforcement in the first place is one thing, but keeping it unaware of you having bypassed it for the duration of the session is another... And quite critical.</p><p></p><p>DSEFix.exe will do the following:</p><p>1. Drop the vulnerable VirtualBox device driver to disk</p><p>2. Create a new Windows Service for the device driver</p><p>3. Start the newly created Windows Service</p><p>4. Exploitation</p><p></p><p>The VBoxDrv.sys will be dropped to <strong>SystemDrive:\\WINDOWS\\System32\\drivers</strong> directory.</p><p></p><p>Therefore a sufficient mitigation for the exploit attack could even be prevention of the vulnerable VirtualBox device driver being allowed to be installed and loaded on the environment. If it cannot, then the exploit stage cannot be reached... And you'd have killed two birds with one stone.</p><p></p><p></p><p>1. Make a generic signature for dsefix.exe</p><p>2. Make a memory scanner</p><p></p><p>Use disassembly to make the signature.</p></blockquote><p></p>
[QUOTE="Deleted member 65228, post: 730814"] Well, if you're loading an unsigned device driver, the last thing you want is for a BSOD to be triggered if the system recognizes there's an unsigned device driver loaded. Bypassing Driver Signature Enforcement in the first place is one thing, but keeping it unaware of you having bypassed it for the duration of the session is another... And quite critical. DSEFix.exe will do the following: 1. Drop the vulnerable VirtualBox device driver to disk 2. Create a new Windows Service for the device driver 3. Start the newly created Windows Service 4. Exploitation The VBoxDrv.sys will be dropped to [B]SystemDrive:\\WINDOWS\\System32\\drivers[/B] directory. Therefore a sufficient mitigation for the exploit attack could even be prevention of the vulnerable VirtualBox device driver being allowed to be installed and loaded on the environment. If it cannot, then the exploit stage cannot be reached... And you'd have killed two birds with one stone. 1. Make a generic signature for dsefix.exe 2. Make a memory scanner Use disassembly to make the signature. [/QUOTE]
Insert quotes…
Verification
Post reply
Top