In other words, when we try to open a new window using the extension-protocol ms-browser-extension: it will always return null. It opens! But, it is not really useful for us because the window.open() returns null instead of a window object, with or without the installed extension. But unfortunately iframes refuse to load the ms-browser-extension: protocol. If we can load it in an iframe and detect its presence (onload/onreadystatechange/whatever) to distinguish it between a default Edge 404 page, we are almost done. In the extensions store I randomly selected the AdGuard blocker. After two clicks it was installed and automatically opened a thank-you page that gave me ideas before even starting the research.
#DETECT SAFE BROWSING 4.8.0 HOW TO#
If you want to learn more about how to detect extensions on Firefox and Chrome, read this paper describing the methodology or visit the amazing Inria site above, but here we will try to achieve the same on Microsoft Edge. Yesterday, Nataliia Bielova tweeted about a site that shows how extensions can be detected on different browsers, however, Microsoft Edge is excluded.īy the way, terrific research and proof of concept from Inria Privatics, Gábor Gulyás, and Nataliia Bielova. Microsoft patched those ones and other variations but today we are going to see how to detect browser extensions installed on Edge. We’ve seen in the past two techniques that allowed the bad guys to detect the presence of particular files (to evade analysts) and even get the application names associated to specific mimeTypes. Attackers love being able to fingerprint their victims.
0 kommentar(er)
