Skip to content
This repository has been archived by the owner on Feb 16, 2024. It is now read-only.

Complex AndroidManifest.xml analysis #35

Open
Razican opened this issue Sep 22, 2016 · 3 comments
Open

Complex AndroidManifest.xml analysis #35

Razican opened this issue Sep 22, 2016 · 3 comments

Comments

@Razican
Copy link
Member

Razican commented Sep 22, 2016

We need to add content providers, receivers, etc. to manifest analysis, and rules to decide what to analyze. Here is the complete list:

  • <provider>:
    • if android:exported="false" everything is OK.
    • if android:exported="true" and any targetSdkVersion or no android:exported and minSdkVersion < 17, we could have a vulnerability:
      • if android:permission or android:readPermission or android:writePermission, only warning.
      • if no permissions, medium or high vulnerability: other apps can read it.
  • <receiver>, <activity>, <activity-alias> or <service>:
    • if android:exported="false" everything is OK.
    • if android:exported="true" we could have a vulnerability:
      • if android:permission, only warning.
      • if no permissions, medium or high vulnerability: other apps can access it.
    • If no android:exported, we could have a vulnerability:
      • if no <intent-filter>, everything is OK.
      • if <intent-filter>:
        • if android:permission, only warning.
        • if no permissions, medium or high vulnerability: other apps can access it.

Analysis from AndroBugs: https://github.com/AndroBugs/AndroBugs_Framework/blob/master/androbugs.py

@Chuky9
Copy link
Member

Chuky9 commented Nov 3, 2016

Complex AndroidManifest.xml analysis implemented but some clarifications are required in order to improve these detections in the next version (0.3.0). That's why this issue will remain openned.

@Chuky9 Chuky9 modified the milestones: SUPER 0.3.0, SUPER 0.2.0 Nov 3, 2016
@Razican
Copy link
Member Author

Razican commented Nov 10, 2016

This depends on #20. We suppose that it will be available before the launch of 0.3.0 with enough time to implement it, so we maintain it for 0.3.0.

@Razican Razican modified the milestones: SUPER 0.3.0, SUPER 0.4.0 Feb 11, 2017
@Razican
Copy link
Member Author

Razican commented Apr 2, 2017

Moving this to SUPER 0.5.0.

@Razican Razican modified the milestones: SUPER 0.5.0, SUPER 0.4.0 Apr 2, 2017
@Razican Razican modified the milestones: SUPER 0.5.0, SUPER 0.6.0 May 10, 2018
@Razican Razican modified the milestones: SUPER 0.6.0, SUPER 0.7.0 Nov 10, 2019
@Razican Razican modified the milestones: SUPER 0.7.0, SUPER 0.6.0 Nov 11, 2019
@Razican Razican modified the milestones: SUPER 0.6.0, SUPER 0.7.0 Mar 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants