550 likes | 752 Views
Erika Chin Adrienne Porter Felt Kate Greenwood David Wagner University of California Berkeley MobiSys 2011. Analyzing Inter-Application Communication in Android. Outline. Introduction Android Overview Intent-based Attack Surfaces ComDroid Evaluation Other mobile Platforms.
E N D
Erika Chin Adrienne Porter Felt Kate Greenwood David Wagner University of California Berkeley MobiSys2011 Analyzing Inter-Application Communication in Android
Outline • Introduction • Android Overview • Intent-based Attack Surfaces • ComDroid • Evaluation • Other mobile Platforms
Introduction • Android’s message passing system can become an attack surface if used incorrectly • Intent • Intents can be used for both intra- and inter-application communication • ComDroid • A tool analyzes Android applications to detect potential instances of vulnerabilities • Personal data loss, corruption, phishing…
Android Overview • Android’s security model differs significantly from the standard desktop security model • The complexity of Android’s message passing system implies it has the largest attack surface
Android Overview • Threat Model Isolation (mem, file..) Isolation (mem, file..)
Android Overview Malicious Intent Activity Activity Activity Intent Intent Intent Service Service Service Fake System Intent BroadcastReceiver BroadcastReceiver BroadcastReceiver System Intent
Android Overview Activity www.bank.com attacker.com ?
Android Overview • This paper do not consider attacks on the OS • Just focus on securing applications from each other
Android Overview • Intents [link] • System broadcast Intents • Only can be sent by the OS • Explicit or implicit
Explicit Intents Name: MapActivity Map App Yelp To: MapActivity Only the specified destination receives this message
Implicit Intents Handles Action: VIEW Map App Yelp Handles Action: DISPLAYTIME Clock App Implicit Intent Action: VIEW
Implicit Intents Handles Action: VIEW Map App Yelp Handles Action: VIEW Browser App Implicit Intent Action: VIEW
Android Overview • Activities • Services • Broadcast Receivers • Content Providers
Android Overview • Activity • Display on screen Advanced Defense Laboratory
Android Overview • Service • Background process Advanced Defense Laboratory
Android Overview • Broadcast Receiver • Asynchronous event notification Advanced Defense Laboratory
Android Overview • Content Provider • Share data between applications • Do not use Intents • Use URI (Uniform Resource Identifier) Advanced Defense Laboratory
Android Overview • Component Declaration • AndroidManifest.xml • To receive Intents… • Service and Activity must be declared in the manifest • Broadcast Receivers can be declared at runtime or in the manifest
Android Overview • Exported Components • EXPORTED flag (in AndroidManifest.xml) • Includes at least one Intent filter • Intent filter • Action, category, data, extra data…
Android Overview • A sender can assign any action, type, or category (certain actions that it only the system can send)
Android Overview • Permission • Normal • Dangerous • Signature • SignatureOrSystem
Common Developer Pattern:Unique Action Strings IMDb App Handles Actions: willUpdateShowtimes, showtimesNoLocationError Showtime Search Results UI Implicit Intent Action: willUpdateShowtimes
Common Developer Pattern:Unique Action Strings IMDb App Handles Actions: willUpdateShowtimes, showtimesNoLocationError Showtime Search Results UI Implicit Intent Action: willUpdateShowtimes
ATTACK #1: Eavesdropping IMDb App Eavesdropping App Handles Action: willUpdateShowtimes, showtimesNoLocationError Showtime Search Malicious Receiver Implicit Intent Action: willUpdateShowtimes Sending Implicit Intents makes communication public
ATTACK #2: Intent Spoofing Malicious Injection App IMDb App Handles Action: willUpdateShowtimes, showtimesNoLocationError Malicious Component Results UI Action: showtimesNoLocationError Receiving Implicit Intents makes the component public
Typical case Attack case
ATTACK #3: Man in the Middle IMDb App Man-in-the-Middle App Handles Action: willUpdateShowtimes, showtimesNoLocation Error Handles Action: willUpdateShowtimes, showtimesNoLocationError Showtime Search Results UI Malicious Receiver Action: willUpdateShowtimes Action: showtimesNoLocation Error
ATTACK #4: System Intent Spoofing • Background – System Broadcast • Event notifications sent by the system • Some can only be sent by the system • Receivers become accessible to all applications when listening for system broadcast
App 1 System Broadcast Component Handles Action: BootCompleted System Notifier App 2 Component Handles Action: BootCompleted Action: BootCompleted App 3 Component Handles Action: BootCompleted
System Intent Spoofing: Failed Attack Malicious App App 1 Handles Action: BootCompleted Malicious Component Component Action: BootCompleted
System Intent Spoofing: Successful Attack Malicious App App 1 Handles Action: BootCompleted Malicious Component Component To: App1.Component
Real World Example: ICE App ICE App: Allows doctors access to medical information on phones Contains a component that listens for the BootCompleted system broadcast On receipt of the Intent, it exits the application and locks the screen
ComDroid • Disassemble application DEX files using Dedexer tool • Parses the disassembled output and logs potential component and Intent vulnerabilities
ComDroid • Permission • Normaland Dangerous • Intent Analysis • Intents, IntentFilters, registers, sinks (e.g., sendBroadcast(), startActivity(), etc.) and components
ComDroid • Intent • Whether it has been made explicit • Whether it has an action • Whether it has any flags set • Whether it has any extra data • Sinks • Implicit or not?
ComDroid • Component Analysis • Public or not? • Main, launching Activity is public but is less likely to be attackable • registerReceiver() • With data / without data • System broadcast • Intent.getAction() • Misuse
ComDroid • Limitation and discussion • Do not distinguish between paths through if and switch statements • False negatives • Pending Intent • Future work