Broken UA spoofing

[billkewl]

AdGuard version

2.11.0.1292

Browser version

No response

OS version

macOS 13.4.1

What filters do you have enabled?

No response

What Stealth Mode options do you have enabled?

Hide your search queries, Send Do-Not-Track signals, Block WebRTC, Block Push API, Block Location API, Hide Referrer from third-parties, Hide your User Agent, Mask your IP address, Remove X-client-Data header, Protect from DPI

Support ticket ID

No response

Issue Details

Steps to reproduce:

1. turn on hide UA in stealth mode
   2.look through http headers or websites like https://browserleaks.com/client-hints

Expected Behavior

No actual UA, OS, desktop or mobile platform, CPU architect, browser info etc. leaked.
http referrer header removed.

Actual Behavior

only http user agent header is spoofed.
SEC-CH-UA, SEC-CH-UA-PLATFORM and the like are not spoofed. OS and browser UA leaked.
http referrer header also leaked.

Screenshots

Screenshot 1:

Additional Information

Is JavaScript API leak avoidable? Please consider improving it if it's also achievable.

Thanks.

[Aydinv13]

@billkewl hello.

You are right, at this moment sec-ch-ua headers aren't being changed but it will be implemented in v1.13 of CoreLibs. The task is already created AdguardTeam/CoreLibs#1764.
I'm closing the current one as a duplicate.

[billkewl]

@Aydinv13
Thanks. What about JavaScript API leak?
Is there any way to prevent it?

[Aydinv13]

@billkewl

What about JavaScript API leak?

Its modification will also be included in the CoreLibs update (v1.13).