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

remove READ_PHONE_STATE #733

Open
ber4444 opened this issue Jan 17, 2024 · 3 comments
Open

remove READ_PHONE_STATE #733

ber4444 opened this issue Jan 17, 2024 · 3 comments
Milestone

Comments

@ber4444
Copy link

ber4444 commented Jan 17, 2024

The SDK adds this permission here:

<uses-permission android:name="android.permission.READ_PHONE_STATE" />

It's a security finding with the following notes:

The listed permissions give access to sensitive user data, and could expose this data. This may also be viewed as a privacy violation or even malware.

Unless required by the App, remove permission requests that are unsafe, unnecessary, or used by known malware. This will ensure that the App is not accessing user private data.

android.permission.READ_PHONE_STATE: This permission allows read only access to phone state. Developers, usually use this permission to detect when the user receives a call. However, this permission also provides the application access to sensitive hardware identifiers such as the IMEI, SimSerialNumber, SubscriberID.

@breedx-splk
Copy link
Contributor

Thanks @ber4444 , we will take this under advisement. I forget the exact specific thing, but I believe that the permission is included so that we can do thorough network detection, especially on older versions of Android. See the NetworkDetector in the upstream OpenTelemetry repository.

I wonder if this is something that we can turn off by default and require developers to opt-into this feature. That would be a breaking change that could come as a surprise to existing users (and would probably require a major version bump as a result).

@ber4444
Copy link
Author

ber4444 commented Jan 25, 2024

Is it not an optional permission in Open telemetry? If not, it should be, and existing users won't notice a thing since they already added this permission, thinking it was mandatory.

@breedx-splk
Copy link
Contributor

It's not currently optional in otel. If you look above your last comment you'll see that I opened an issue there to also track this.

I see your point, though, that if it's already brought it from upstream that it may not be needed here.

@breedx-splk breedx-splk added this to the 2.0 milestone Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants