Phishing attacks carried out by injecting malicious content in legitimate traffic are difficult to detect when attackers use an embedded browser framework or any other automated tool for authentication.
For example, the embedded browser framework Google offers Chromium Embedded Framework (CEF) that allows embedding Chromium-based browsers in other applications.
Google announced that starting from June, it will block sign-ins from these frameworks.
“However, one form of phishing, known as “man in the middle” (MITM), is hard to detect when an embedded browser framework (e.g., Chromium Embedded Framework – CEF) or another automation platform is being used for authentication. MITM intercepts the communications between a
Google suggests developers currently using CEF for authentication to switch to the browser-based OAuth authentication.
The browser-based OAuth authentication also allows users to see the full URL of the page where they are entering their credentials, this could help them to avoid phishing websites mimicking legit ones.
“The solution for developers currently using CEF for authentication is the same: browser-based OAuth authentication. Aside from being secure, it also enables users to see the full URL of the page where they are entering their credentials, reinforcing good anti-phishing practices,” continues Google.
“If you are a developer with an app that requires access to Google Account data, switch to using
(SecurityAffairs – hacking, MiTM phishing attack)
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.