Jump to content

[SOLVED] Browsers not opening with MBAE & Comodo


TheDukeUK

Recommended Posts

IE11 fails to start on Windows 7 with MBAE On. It has worked fine up until today and the only things I have done recently is upgrade Comodo Endpoint Security to 8.2, Update to Adobe Acrobat Reader DC from X11, Update TomTom Home and apply a Windows Update KB2952664. If I stop protection with MBAE IE starts up fine or if I uninstall MBAE it starts fine. I have disabled all add ons but still IE will not start with MBAE enabled. I have done a Malwarebytes Full Scan recently and I am 100% sure I have not been anywhere to acquire an exploit in the past week.

 

I know that it was working fine on 25th July 2015 and that was the last time I used IE till today when I either get a popup from MBAE or an egg timer then IE just closes.

 

Zip of Programdata as requested attached

Malwarebytes Anti-Exploit.zip

Link to post
Share on other sites

There is a known issue with Comodo. Try the workaround mentioned in the Known Issues list but instead of adding the Firefox folder, add the IE folder.

 

Excuse me I let this got the first time but Comodo is the top Internet Security Company in the world who do a variety of security products. Two such products which I believe you refer to are Comodo Endpoint Security and Comodo Internet Security. The issue is not with either of these products it is with your MalwareBytes Anti Exploit product giving a False Positive rendering it next to useless. Instead of providing workarounds it would behove you to fix your product and make it more accurate.

The "workaround" you suggest is dated  Oct 19 2013 and you still have not fixed the false positive reading in your software.

However I have added C:\Program Files\Internet Explorer and C:\Program Files (x86)\Internet Explorer to the HIPS -> Detect shellcode injections -> Exclusion list in Comodo Endpoint Security and can now open IE11 with MBAE enabled.

Disabling a security feature in one product to get round a deficiency in another is hardly a satisfactory "workaround" as it leaves one more vulnerable instead of more protected which should be the aim of all internet security companies.

I have installed CIS and MBAE on dozens of Friends computers and would appreciate a more active interest from your company in fixing this problem with your software please. So I do not have to implement this, almost 2 year old, "workaround" on them all. Thanks in Advance.

Link to post
Share on other sites

  • Staff

The issue (and consequent workaround) is actually pretty recent. The Known Issues list is from Oct 2013, but it is a live post which changes over time as new versions of MBAE are released.

 

The fix from our end is on our backlog, but it is to be expected that products that have similar anti-exploit technology, like MBAE and EMET, might conflict like this. This is not to say that Comodo has anything near what MBAE does, as the source of the conflict is not due to conflicting mitigations in this case.

Link to post
Share on other sites

The issue (and consequent workaround) is actually pretty recent. The Known Issues list is from Oct 2013, but it is a live post which changes over time as new versions of MBAE are released.

 

The fix from our end is on our backlog, but it is to be expected that products that have similar anti-exploit technology, like MBAE and EMET, might conflict like this. This is not to say that Comodo has anything near what MBAE does, as the source of the conflict is not due to conflicting mitigations in this case.

 

Thank you ... it possible please would you reply to this thread when there is a fix released for it please so I may update the dozens of friends computers I have installed your MBAE on ?

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.