Solarlynx Posted November 20, 2014 ID:910448 Share Posted November 20, 2014 Hi! Google Chrome starts OK with MBAE free. But with this latest experimental build it doesn't start. Sometimes, but not every time, MBAE says it blocked an exploit attempt. When the Chrome shield is deactivated, the browser starts OK. Link to post Share on other sites More sharing options...
Staff pbust Posted November 20, 2014 Staff ID:910473 Share Posted November 20, 2014 Hi Solarlynx, welcome to the forum. Can you please post your files from the MBAE user data directory (C:\ProgramData\Malwarebytes Anti-Exploit) as well as a DDS or FRST log? Link to post Share on other sites More sharing options...
Staff pbust Posted November 21, 2014 Staff ID:910660 Share Posted November 21, 2014 New Experimental build 1012 published here:https://forums.malwarebytes.org/index.php?/topic/160317-mbae-experimental-10531012/ Link to post Share on other sites More sharing options...
Solarlynx Posted November 21, 2014 Author ID:910788 Share Posted November 21, 2014 Hello!The same prob with 1012. Here the files from the MBAE user data directory and FRST log. Malwarebytes Anti-Exploit.rarFRST.rar Link to post Share on other sites More sharing options...
Staff pbust Posted November 22, 2014 Staff ID:911355 Share Posted November 22, 2014 Can you try disabling the TotalSecurity360 webshield module as well as the 360 Chrome 360InternetProtection extension to see if that makes a difference? Also it is worth trying MBAE 1.04 to see if the problem persists. The MBAE experimental builds are signed by ZVL instead of Malwarebytes, so this could be the source of the conflict with TotalSecurity360 as the ZVL digital signature might not be in their whitelist. Link to post Share on other sites More sharing options...
Solarlynx Posted November 24, 2014 Author ID:911971 Share Posted November 24, 2014 It doesn't work. Chrome doesn't launch with "TotalSecurity360 webshield module" and the "360 Chrome 360InternetProtection extension" disabled, with both 1.04 and 1.05. Link to post Share on other sites More sharing options...
Staff pbust Posted November 24, 2014 Staff ID:911982 Share Posted November 24, 2014 Thanks for testing. What if you completely uninstall TotalSecurity360 and Comodo Firewall? After uninstalling them, reboot and then reinstall MBAE to see if it makes a difference. Also you mentioned the same problem happened with 1.04, but on your first post you mentioned that it was ok with MBAE Free (aka 1.04). Did it stop working recently and was working before? Link to post Share on other sites More sharing options...
Solarlynx Posted November 25, 2014 Author ID:912365 Share Posted November 25, 2014 Chrome started when I just uninstalled Comodo FW, without rebooting and reinstalling MBAE. As for 1.04 free I'm sorry I confused it with experimental build 1.05.3.1011. What I wrote with respect to 1.04 I meant 1011 build. I'm sorry. So is it possible to make MBAE experimental get along with Comodo FW so that Chrome starts? Thank you. Link to post Share on other sites More sharing options...
Staff pbust Posted November 25, 2014 Staff ID:912366 Share Posted November 25, 2014 Based on this feedback then I think it's safe to say that what Comodo is chocking on is the digital signature. Once MBAE 1.05 becomes final early next week this will be solved as it will be digitally signed by Malwarebytes. Link to post Share on other sites More sharing options...
Solarlynx Posted November 25, 2014 Author ID:912415 Share Posted November 25, 2014 When I tried to include signature from running mbae.exe, CF said it already has ZeroVulnerabilityLabs in the list.Then I added all files from folder "C:\Program Files (x86)\Malwarebytes Anti-Exploit" to trusted. Anyway shielded Chrome doesn't start. Maybe the problem is not in the digital signature? Link to post Share on other sites More sharing options...
Staff pbust Posted November 25, 2014 Staff ID:912418 Share Posted November 25, 2014 If I remember correctly we had this problem before with Comodo. In addition to the user-managed certificates, they also have some internal overflow protection for browsers to which the user-based certificates do not apply. They had to exclude us manually from that feature. Try MBAE 1.04. If the problem goes away then I am very certain the problem is this one. Link to post Share on other sites More sharing options...
Solarlynx Posted November 26, 2014 Author ID:912747 Share Posted November 26, 2014 Yes, with the 1.04 the problem goes away. So next 1.05 free will be signed correctly and therefore is expected without this problem, isn't it? Link to post Share on other sites More sharing options...
Solarlynx Posted November 26, 2014 Author ID:912759 Share Posted November 26, 2014 Btw can you sign next experimental builds so they get along with CF? Than I will have experimental builds. Link to post Share on other sites More sharing options...
Staff pbust Posted November 26, 2014 Staff ID:912801 Share Posted November 26, 2014 Yes, the problem will go away next week when we release MBAE 1.05. Link to post Share on other sites More sharing options...
Solarlynx Posted November 26, 2014 Author ID:912802 Share Posted November 26, 2014 OK, thank you. Link to post Share on other sites More sharing options...
Solarlynx Posted November 28, 2014 Author ID:913471 Share Posted November 28, 2014 By the way I have Comodo Internet Security on other my PC. CIS gets along with MBAE experimental 1.05.3.1012 without any problems. CIS and CF are of the same latest version on my PCs. Link to post Share on other sites More sharing options...
Staff pbust Posted December 1, 2014 Staff ID:914422 Share Posted December 1, 2014 MBAE 1.05.1.1014 final version has just been released. More info:https://forums.malwarebytes.org/index.php?/topic/161643-malwarebytes-anti-exploit-10511014/ Link to post Share on other sites More sharing options...
Solarlynx Posted December 2, 2014 Author ID:914673 Share Posted December 2, 2014 No, with this new MBAE 1.05.1.1014 chrome again doesn't start. Link to post Share on other sites More sharing options...
Staff pbust Posted December 2, 2014 Staff ID:914674 Share Posted December 2, 2014 QA has replicated the issue. We'll be contacting Comodo to whitelist our API hooks within the browser. You can follow-up on the issue here:https://forums.malwarebytes.org/index.php?/topic/161677-mbae-comodo-firewall-conflict-blocks-chrome/ Link to post Share on other sites More sharing options...
Solarlynx Posted December 2, 2014 Author ID:914677 Share Posted December 2, 2014 OK, thank you. Anticipating... Link to post Share on other sites More sharing options...
Solarlynx Posted December 12, 2014 Author ID:918687 Share Posted December 12, 2014 It seems they fixed the problem. Chrome starts OK with MBAE + new release of CF 8.0.0.4344. Link to post Share on other sites More sharing options...
Staff pbust Posted December 13, 2014 Staff ID:918824 Share Posted December 13, 2014 Thanks for confirming Solarlynx! Our QA has also tested this and they also confirm the issue is fixed. Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now