Android Permission Analysis System for Security Risk Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The rapid growth of the Android market has led to increased security risks due to excessive permission declarations in applications, which can result in personal information leakage and privilege escalation attacks, as there is no formal screening procedure in place to prevent such issues.
Innovation Solution
An apparatus and method for analyzing application permissions on Android devices, involving the acquisition of executable files, unpackaging, reverse engineering, and analysis to detect excessive or undeclared permissions, comparing declared and used permissions against pre-defined patterns to identify and block security risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the Android market allows applications to be uploaded without formal screening, then the ease of operation and accessibility for users is improved, but security risks increase due to excessive permission declarations and undeclared permission usage
Solution Approach 1:
The patent performs permission analysis on applications before they are officially released to the market. The analysis system examines the androidmanifest.xml file and reverse-engineers the application code to detect excessive permission declarations and undeclared permission usage in advance, allowing the market administrator to screen and block risky applications before they reach users
Solution Approach 2:
The patent introduces an intermediate permission analysis system that acts as a mediator between the application uploader and the end user. This system includes modules to extract permission information from manifest files, reverse-engineer application code, compare declared vs. actual permission usage, and generate risk reports that are sent to the market administrator for final screening decisions
2Reliability
If permission analysis and screening procedures are implemented for applications, then security reliability is improved, but the complexity of the application release process increases
Solution Approach 1:
The patent divides the permission analysis process into distinct modular components: (1) extracting permission information from androidmanifest.xml files, (2) reverse-engineering application code to detect actual permission usage, (3) comparing declared permissions with actual usage, and (4) generating risk reports. This segmentation allows each module to be independently implemented and managed, reducing overall system complexity
Solution Approach 2:
The analysis system automatically performs permission detection and risk assessment without requiring manual intervention. The system self-services by automatically extracting manifest information, reverse-engineering code, comparing permission declarations with actual usage patterns, and generating standardized risk reports that are directly sent to administrators, minimizing the need for complex manual screening procedures
3Adaptability or versatility
If developers declare more permissions in the application manifest, then the adaptability and functionality of the application are improved, but the risk of information leakage and privilege escalation attacks increases
Solution Approach 1:
The patent implements a feedback mechanism where the analysis system provides detailed reports to developers about excessive permission declarations and undeclared permission usage. The system compares what permissions are declared in the manifest versus what permissions are actually used in the code, giving developers specific feedback on which permissions can be removed or properly declared, allowing them to optimize their applications for both functionality and security
Data Source
AI summary
An apparatus for analyzing a permission of an application for a mobile device, the apparatus comprising: an executable file acquisition unit; a file extraction module; and an execution permission analyzing module configured to detect a security risk which can be caused by the permission on the basis of the permission described in the extracted file, wherein the information related to the permission of the application includes information on permission that is declared in the application, permission that the application uses and a function that uses the permission of the application.