Showing posts with label android thesis work. Show all posts
Showing posts with label android thesis work. Show all posts

Tuesday, 20 October 2015

Vulhunter: Toward Discovering Vulnerabilities In Android Applications



ABSTRACT:
With the prosperity of the Android app economy, many apps have been published and sold in various markets. However, short development cycles and insufficient security development guidelines have led to many vulnerable apps. Although some systems have been developed for automatically discovering specific vulnerabilities in apps, their effectiveness and efficiency are usually restricted because of the exponential growth of paths to examine and simplified assumptions. In this article, the authors propose a new static-analysis framework for facilitating security analysts to detect vulnerable apps from three aspects. First, they propose an app property graph (APG), a new data structure containing detailed and precise information from apps. Second, by modeling app-related vulnerabilities as graph traversals, the authors conduct graph traversals over APGs to identify vulnerable apps for easing the identification process. Third, they reduce the workload of manual verification by removing infeasible paths and generating attack inputs whenever possible. They have implemented the framework in a system named VulHunter with 9,145 lines of Java code and modeled five types of vulnerabilities. Checking 557 popular apps that are randomly collected from Google Play and have at least 1 million installations, the authors found that 375 apps (67.3 percent) have at least one vulnerability.
AIM
The aim of this paper is a new static-analysis framework for facilitating security analysts to detect vulnerable apps from three aspects.
SCOPE
The scope of this tends to implemented the framework in a system named VulHunter with 9,145 lines of Java code and modeled five types of vulnerabilities.
EXISTING SYSTEM:
Existing research on automatic vulnerability discovery for applications (“apps”) usually focuses on several specific types of vulnerabilities because of the undecidability of the generic problem of spotting program vulnerabilities For example, ComDroid aims at Intent related issues (that is, unauthorized Intent receipt and Intent spoofing). SMV-Hunter detects SSL and Transport Layer Security (TLS) man-in-the-middle vulnerabilities., Content Scope examines the vulnerabilities of an unprotected content provider. Android Leaks uncovers potential private information leakages. Woodpecker targets capability leak vulnerabilities. CHEX discovers component hijacking vulnerabilities. However, these systems’ effectiveness and efficiency are usually restricted in practice due to the exponential growth of paths to examine, simplified assumptions, and the limited number of vulnerability patterns.1,8 Moreover, it is not easy to extend these systems to capture new vulnerabilities, although they share some common, components (such as constructing control-flow graphs and dataflow graphs).
DISADVANTAGES:

  1. It is not easy to extend these systems to capture new vulnerabilities, although they share some common, components (such as constructing control-flow graphs and dataflow graphs).
  2. They did not discover vulnerable apps, and it is not clear how SCA processes those apps.

PROPOSED SYSTEM:
In this project, propose a new static-analysis framework to facilitate vulnerability discovery for apps by extracting detailed and precise information from apps and easing the identification process. Moreover, the framework can reduce the manual-verification workload by performing slicing and filtering out infeasible paths. To our knowledge, existing approaches cannot achieve these goals simultaneously. Moreover, defining app property graphs (APGs) and employing graph databases can scale up the vulnerability discovery process. Researchers are exploring an alternative vulnerability-discovery approach of facilitating security analysts by providing detailed and precise information and expert knowledge. The work closest to our approach is the code property graph (CPG),1 which combines an abstract syntax tree (AST), control-flow graph (CFG), and program dependency graph (PDG) to represent C source codes and model common vulnerabilities as graph traversals. Therefore, finding potential vulnerabilities is turned into performing graph traversals over CPGs with much better performance in terms of accuracy and flexibility. Although we also model vulnerabilities as graph traversals and conduct graph traversals to find vulnerable apps, significant differences exist between the two approaches.
ADVANTAGES

  1. Capturing vulnerabilities is made easy and alsomodeling vulnerabilities become easy as per graph traversals.
  2. It reduces false positives and optimizes queries according to vulnerabilities pattern.

SYSTEM ARCHITECTURE:



SYSTEM CONFIGURATION

HARDWARE REQUIREMENTS:-

·                 Processor   -   Pentium –III

·                Speed                -    1.1 Ghz
·                RAM                 -    256 MB(min)
·                Hard Disk         -   20 GB
·                Floppy Drive    -    1.44 MB
·                Key Board                 -    Standard Windows Keyboard
·                Mouse               -    Two or Three Button Mouse
·                Monitor             -    SVGA

SOFTWARE REQUIREMENTS:-

·                Operating System      : Android OS                                      
·                Front End                  : JAVA
·                Database                  : Sqlite
·                Tool                           :Eclipse


REFERENCE:
Chenxiong Qian Xiapu Luo ; Yu Le ; Guofei Gu “VULHUNTER: TOWARD DISCOVERING VULNERABILITIES IN ANDROID APPLICATIONS”, IEEE Transactions on Micro, Volume 35 ,  Issue 1,Jan.-Feb. 2015

CONTEXT-BASED ACCESS CONTROL SYSTEMS FOR MOBILE DEVICES



ABSTRACT:
Mobile Android applications often have access to sensitive data and resources on the user device. Misuse of this data by malicious applications may result in privacy breaches and sensitive data leakage. An example would be a malicious application surreptitiously recording a confidential business conversation. The problem arises from the fact that Android users do not have control over the application capabilities once the applications have been granted the requested privileges upon installation. In many cases, however, whether an application may get a privilege depends on the specific user context and thus we need a context-based access control mechanism by which privileges can be dynamically granted or revoked to applications based on the specific context of the user. In this paper we propose such an access control mechanism. Our implementation of context differentiates between closely located sub-areas within the same location. We have modified the Android operating system so that context-based access control restrictions can be specified and enforced. We have performed several experiments to assess the efficiency of our access control mechanism and the accuracy of context detection.
AIM
The aim of this paper is our implementation of context differentiates between closely located sub-areas within the same location.
SCOPE
The scope of this paper tends to have performed several experiments to assess the efficiency of our access control mechanism and the accuracy of context detection.
EXISTING SYSTEM:
Security for mobile operating systems focuses on restricting applications from accessing sensitive data and resources, but mostly lacks efficient techniques for enforcing those restrictions according to fine-grained contexts that differentiate between closely located subareas. Moreover, most of this work has focused on developing policy systems that do not restrict privileges per application and are only effective system-wide. So User disable all applications from using the camera and any device resources and privileges that employers restrict while at work, while the user device can retain all its original privileges outside the work area.
DISADVANTAGES
·      Do not cover all the possible ways in which applications can access user data and device resources.
·      The User leakage of Their privacy.
·  Existing location-based policy systems are not accurate enough to differentiate between nearby locations without extra hardware or location devices.
PROPOSED SYSTEM:
In this paper, we propose a context-based access control (CBAC) mechanism for Android systems that allows smartphone users to set configuration policies over their applications’ usage of device resources and services at different contexts. Through the CBAC mechanism, users can, for example, set restricted privileges for device applications when using the device at work, and device applications may re-gain their original privileges when the device is used at home. This change in device privileges is automatically applied as soon as the user device matches a pre-defined context of a user-defined policy. The user can also specify a default set of policies to be applied when the user is located in a non-previously defined location. Configured policy restrictions are defined according to the accessible device resources, services, and permissions that are granted to applications at installation time. Such policies define which services are offered by the device and
limit the device and user information accessibility. Policy restrictions are linked to context and are configured by the device user. We define context according to location and time.
ADVANTAGES
 Applications should not be able to fake the location or time of the device.
Can develop securer and more acceptable applications for end users.
SYSTEM ARCHITECTURE:




SYSTEM CONFIGURATION

HARDWARE REQUIREMENTS:-

·                 Processor   -   Pentium –III

·                Speed                -    1.1 Ghz
·                RAM                 -    256 MB(min)
·                Hard Disk         -   20 GB
·                Floppy Drive    -    1.44 MB
·                Key Board         -    Standard Windows Keyboard
·                Mouse               -    Two or Three Button Mouse
·                Monitor             -    SVGA

SOFTWARE REQUIREMENTS:-

·                Operating System      : Android OS                                      
·                Front End                  : JAVA
·                Database                  : Sqlite
·                Tool                           :Eclipse


REFERENCE:
Oluwatimi, O. Bertino, E., “CONTEXT-BASED ACCESS CONTROL SYSTEMS FOR MOBILE DEVICES”, IEEE Transactions on Dependable and Secure Computing  Volume 12 ,  Issue 2 April 2014