microg / microg/GmsCore

EXTENDED_ACCESS permission

Open
#149 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

confirmed security
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

The EXTENDED_ACCESS permission is designed to provide features to app that in original Google Play Services are only available to Google apps (checked using signature). The security model of this functionality is not well-designed and should be improved

  • The permission should never be granted silently without user consent
  • Different data should have separated access, e.g. Google Plus friend list is not accessible to apps only requiring access to Android Wear details.
    This could be realized by splitting up EXTENDED_ACCESS permission further or independently from the actual permission request (dynamically)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Begin by locating EXTENDED_ACCESS and tracing how it is granted and which data it protects; done means user consent is required and access to different data is separated as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
authorization, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.