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
Video Reviews - Security and Privacy
Comodo Cloud AV - Autosandbox only - petya bypassed
Message
<blockquote data-quote="Wave" data-source="post: 590465"><p>Not sure why COM would be related to the Master Boot Record - the MBR is the first sector on the disk, it's not even 32-bit/64-bit (but it would be 16-bit ASM since the OS hasn't even loaded yet so the memory is even more limited and the processor can only make use of 16-bit registers)... It's also essential that it's exactly 512 bytes in size and has the boot signature at the end of it (55AA).</p><p></p><p>All Comodo need to do is use a device driver to restrict access to write to the MBR for the isolated program, problem solved. I'm surprised they didn't do it already for CCAV? Does it protect against MBR modifications in the sandbox from the firewall version?</p><p></p><p>Or they can just trick programs modifying it into believing they did when it didn't change anything.</p></blockquote><p></p>
[QUOTE="Wave, post: 590465"] Not sure why COM would be related to the Master Boot Record - the MBR is the first sector on the disk, it's not even 32-bit/64-bit (but it would be 16-bit ASM since the OS hasn't even loaded yet so the memory is even more limited and the processor can only make use of 16-bit registers)... It's also essential that it's exactly 512 bytes in size and has the boot signature at the end of it (55AA). All Comodo need to do is use a device driver to restrict access to write to the MBR for the isolated program, problem solved. I'm surprised they didn't do it already for CCAV? Does it protect against MBR modifications in the sandbox from the firewall version? Or they can just trick programs modifying it into believing they did when it didn't change anything. [/QUOTE]
Insert quotes…
Verification
Post reply
Top