Android gives ‘no permissions’ apps access to sensitive info
Thanks in large part to Android's history of lax app policing, Google's mobile operating system has been criticized as insecure. — But now it appears that apps with no permissions pose a new threat, gaining access …
Context & Ripple Effects
Android's app-security record already included reports of private-data exposure by Android apps and researchers' findings of leaks in pre-installed apps. Those cases put scrutiny on software that requested access; this report challenges the assumption that a clean permission screen signals safety.
The finding compounds the Android image problem identified in March 2012, because Google’s permission disclosures are meant to be the user-facing boundary between an app and sensitive information.
First-order effects
- Android users cannot treat an app’s lack of declared permissions as a reliable indication that it cannot reach sensitive information.
- Google faces pressure to examine the paths through which Android exposes sensitive data, rather than relying solely on an app’s declared permission list.
Second-order effects
- Developers whose apps legitimately need sensitive data face a less credible permission model, making trust in Android Market listings more dependent on Google’s policing.
- Security researchers and app-review services gain a clearer reason to test behavior beyond declared permissions, since the manifest alone may not reveal an app’s access.
Third-order effects
- If recurring disclosure failures persist, Android governance shifts from a developer-declared permission model toward controls and review that verify what apps actually access.
- The episode reinforces incident-led permissioning: security flaws, rather than the original permission design, drive the rules users and developers must navigate.
The trend: Android’s security challenge is moving from visible permission requests toward governance of the data-access paths that users cannot readily inspect.