Android : Unsafe interprocess communication

Unsafe interprocess communication methods are used. This can lead to the loss of valuable data confidentiality, phishing attacks and denial of service attacks.

Interprocess communication in Android can be carried out using Intent objects. Intent handler parameters are defined in the Manifest file of the applications. If the message receiver is specified implicitly or a broadcast messaging mechanism is used, the data contained in these messages may be compromised. Besides, malicious applications can use mechanisms of delegation of process control such as implicit calls of application components or objects such as PendingIntent for control flow hijacking and phishing attacks.

Dangerous types of objects are Activity, Service, BroadcastReceiver, and ContentProvider, which are open to communication with other applications and calls not related to Android system calls (such as android.intent.action.MAIN). Activity and Service objects are by default open to communication, if intent-filter is used to determine an implicit call; BroadcastReceiver is open for communication by default. Intent confidential information hijacking and control flow hijacking are possible. If non-system calls are accepted, an attacker can carry out a denial of service attack through a malicious application, change the behavior of the application, or cause it to crash.

ContentProvider is designed for sharing data across application and is also open by default. It should be regarded as a vulnerability because ContentProvider can contain sensitive data or have an ability to modify important application data.