Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Android] Device/user information leaking when tested #15322

Closed
Brave-Matt opened this issue Apr 15, 2021 · 3 comments · Fixed by brave/brave-core#8562
Closed

[Android] Device/user information leaking when tested #15322

Brave-Matt opened this issue Apr 15, 2021 · 3 comments · Fixed by brave/brave-core#8562

Comments

@Brave-Matt
Copy link

Description

Android build of the app is leaking browser and device info when tested. ipleak.net (for example) was able to pull pretty much everything about my device and/or location. Appears to be a regression of:
#12638

Images are from Nightly build but issue seems to be present on Beta and stable as well:
image

Steps to reproduce

  1. Visit ipleak.net or similar site on Brave Android
  2. Run test

Actual result

Device and user info is leaked.

Expected result

Information should not leak.

Issue reproduces how often

Easily/always

Version/Channel Information:

v1.22.71

  • Can you reproduce this issue with the current Play Store version? Yes
  • Can you reproduce this issue with the current Play Store Beta version? Yes
  • Can you reproduce this issue with the current Play Store Nightly version? Yes

Additional information

User report of the issue:
https://community.brave.com/t/phone-model-leaking-in-brave/233082/7

@Brave-Matt Brave-Matt added the OS/Android Fixes related to Android browser functionality label Apr 15, 2021
@srirambv
Copy link
Contributor

Fixed as part of #14740

@srirambv
Copy link
Contributor

Verification passed on the following devices with Android 10 running 1.23.73 x64 build

  • Verified no device info is leaked
OnePlus 6T (Android 10) Samsung Tab A (Android 10)

@kjozwiak
Copy link
Member

We'll use #15372 for the release notes as it's basically the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants