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
Software
Security Apps
Comodo
Comodo and Weaponized Documents
Message
<blockquote data-quote="AtlBo" data-source="post: 809882" data-attributes="member: 32547"><p>Yes, that's what I got, and it's more or less bullet proof I think. My question is in memory exploit that is able to do all the work without creating/downloading files. I'm specifially thinking of an exploit of Windows like with Eternal Blue/Double Pulsar. The attacks were stopped when a file was created (VoodooShield and some others). I think Cruelsister did a video on Comodo beating EB/DB can't remember. So the idea is exploited browser attempts to exploit Windows all from memory. I can see Comodo HIPs activating here, but, at the very least, I would like to see an auto-block of the activity, even though Chrome as the example is a trusted application.</p><p></p><p>I know Comodo HIPs (Safe Mode) will automatically respond if anything attempts to change the memory of anything in the Windows folder, but this is doomsday scenario here. That's why I feel that Comodo, as good as it is, might be able to go a little bit deeper with auto-blocks and maybe some kind of different alert (really a notification) of the block. This stuff is scary, and I know hackers are working around the clock to get to EB/DB types of exploits for then exploiting via meltdown and spectre...</p><p></p><p>I think heuristic command line on, Comodo is, again, bullet-proof, but you see so many files with so many strange names. For me, so many decisions about these files without some special type of warning and/or auto-block is a recipe for problems. I say so, not because users get too weary or even the risk of a mistake. It's just easy to get lost in all the alerts looking the same. I have numerous times been allowing a sequence of HIPs alerts, only to double-click and allow activity on a following alert which I didn't intend to allow. Sounds like a little thing, but, for me, it's super annoying when you are going to the lengths Comodo requires to keep the run-time environment clean and protected...</p></blockquote><p></p>
[QUOTE="AtlBo, post: 809882, member: 32547"] Yes, that's what I got, and it's more or less bullet proof I think. My question is in memory exploit that is able to do all the work without creating/downloading files. I'm specifially thinking of an exploit of Windows like with Eternal Blue/Double Pulsar. The attacks were stopped when a file was created (VoodooShield and some others). I think Cruelsister did a video on Comodo beating EB/DB can't remember. So the idea is exploited browser attempts to exploit Windows all from memory. I can see Comodo HIPs activating here, but, at the very least, I would like to see an auto-block of the activity, even though Chrome as the example is a trusted application. I know Comodo HIPs (Safe Mode) will automatically respond if anything attempts to change the memory of anything in the Windows folder, but this is doomsday scenario here. That's why I feel that Comodo, as good as it is, might be able to go a little bit deeper with auto-blocks and maybe some kind of different alert (really a notification) of the block. This stuff is scary, and I know hackers are working around the clock to get to EB/DB types of exploits for then exploiting via meltdown and spectre... I think heuristic command line on, Comodo is, again, bullet-proof, but you see so many files with so many strange names. For me, so many decisions about these files without some special type of warning and/or auto-block is a recipe for problems. I say so, not because users get too weary or even the risk of a mistake. It's just easy to get lost in all the alerts looking the same. I have numerous times been allowing a sequence of HIPs alerts, only to double-click and allow activity on a following alert which I didn't intend to allow. Sounds like a little thing, but, for me, it's super annoying when you are going to the lengths Comodo requires to keep the run-time environment clean and protected... [/QUOTE]
Insert quotes…
Verification
Post reply
Top