Detected on Chromium 110

[wmetryka]

Describe the bug

Trying to use Selenium to get through Google Identity Provider and it throws the "unsafe browser" error at me. Seems like it got patched alongside undetected_chromedriver.

Environment:

• OS: Windows
• OS-Version: 10
• Browser: Chromium 110

[kaliiiiiiiiii]

@wmetryka Thanks for your report.

profiles.Windows and profiles.Android are still based on chrome-version 107. It seems like cloufare, google and others detect the chrome-version based on CSS and Window features and match with the reported values.
Looking into the google-chrome version-history, we can see, that from version 109 to 110, the Layout-Engine and V8-engine went one version up.

Changing the versions to:

• Andoid:

profile = {"cdp":{"touch":True,"maxtouchpoints":5,"emulation":{"mobile":True,"width":385,"height":833,"deviceScaleFactor":4,"screenOrientation":{"type":"portraitPrimary","angle":0}},"useragent":{"platform":"Linux aarch64","acceptLanguage":"de-CH","userAgent":"Mozilla/5.0 (Linux; Android 11; HD1913) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Mobile Safari/537.36","userAgentMetadata":{"brands":[{"brand":"Google Chrome","version":"111"},{"brand":"Not(A:Brand","version":"8"},{"brand":"Chromium","version":"111"}],"fullVersionList":[{"brand":"Google Chrome","version":"111.0.5563.58"},{"brand":"Not(A:Brand","version":"8.0.0.0"},{"brand":"Chromium","version":"111.0.5563.58"}],"fullVersion":"111.0.5563.58","platform":"Android","platformVersion":"11.0.0","architecture":"","model":"HD1913","mobile":True,"bitness":"","wow64":False}}}}

• Windows

profile = {"cdp":{"touch":True,"maxtouchpoints":10,"emulation":{"mobile":False,"width":1280,"height":720,"deviceScaleFactor":1.5,"screenOrientation":{"type":"landscapePrimary","angle":0}},"useragent":{"platform":"Win32","acceptLanguage":"de-DE","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36","userAgentMetadata":{"brands":[{"brand":"Google Chrome","version":"111"},{"brand":"Not(A:Brand","version":"8"},{"brand":"Chromium","version":"111"}],"fullVersionList":[{"brand":"Google Chrome","version":"111.0.5563.65"},{"brand":"Not(A:Brand","version":"8.0.0.0"},{"brand":"Chromium","version":"111.0.5563.65"}],"fullVersion":"111.0.5563.65","platform":"Windows","platformVersion":"10.0.0","architecture":"x86","model":"","mobile":False,"bitness":"64","wow64":False}}}}

for chrome-111, this fixes the issue for me.

Edit:

Now, the version of the current browser gets automatically patched since version = 2.2.5.5

[kaliiiiiiiiii]

Fixed with 84f3d16 | version = 2.2.5.5