[Google Chrome block with new Trusteer Rapport]

21 minutes ago, pbust said:

We think we've solved this issue. Please download and install the following build on top of your existing version:

https://malwarebytes.box.com/s/croim8lq4hz5fyk6zfqsmxkxwsavbopo

After upgrading, open MBAE -> Settings -> Advanced settings -> Restore defaults -> Reboot

Let us know if it solves the Trusteer bug.

 

Seems to work for me.  No crashes.  I'll try it out for a couple days to test.

Thanks!!

[Google Chrome block with new Trusteer Rapport]

38 minutes ago, mistertonmick said:

just to add to my above post it was only the advanced memory protection that caused the stopping of chrome,CALL ROP is working OK.

Me too.  I updated Chrome manually and verified the latest Trusteer was on there.  Still crashed, but after removing just the Advanced Memory Protection setting for Chrome, now all is good again.  The CALL ROP is activated.  So, we're making progress I think.

 

[Google Chrome block with new Trusteer Rapport]

9 minutes ago, scottorn said:

FCA711 - The workaround worked! Huge thanks.

Does this expose us to hackers? I'm nervous about turning off any features.

That's my question as well.  I wish they would just come out with a fix and not require this workaround.  Turning off features is like punching holes in the security, so it's probably not ideal in the log run.

 

[Google Chrome block with new Trusteer Rapport]

For me, I had to do BOTH of these workarounds:

MBAE -> Settings -> Advanced Settings -> OS Bypass Protection -> CALL ROP gadget protection (32/64) -> uncheck for Chrome -> Apply

MBAE -> Settings -> Advanced Settings -> Advanced Memory Protection -> Malicious return address detection -> uncheck for Chrome -> Apply

 

I have both Chrome and Trusteer Rappport.  If I do the workarounds, Chrome works OK.

If I shutdown Trusteer first, Chrome opens OK.

Don't know what's causing the conflict, but it's definitely MBAE/Trusteer combo that interferes with Chrome opening.