...
Chin, et al., [Chin 2011] describe describes malicious activity launch: "Exported Activities can be launched by other applications with either explicit or implicit Intents. This attack is analogous to cross-site request forgeries (CSRF) on websites" and malicious service launch: "A malicious Service launch is similar to a malicious Activity launch, but Services typically rely on input data more heavily than Activities. Consequently, a malicious launch attack where the Intent contains data is more likely to put a Service at risk. Additionally, there are more opportunities for a bound Service to return private data to its caller because Services often provide extensive interfaces that let their binders make many method calls."
...
Compliant Solution (Checking Caller's Identity)
In this compliant solution the caller's identity is checked before any action is taken:
| Code Block | ||
|---|---|---|
| ||
TBD |
Compliant Solution (Setting Permission Requirements)
This compliant solution shows the permissions set in the manifest that prevent a malicious application from triggering an inappropriate action:
| Code Block | ||
|---|---|---|
| ||
TBD |
...
Automatic detection of the receipt of an intent is straightforward. It is not feasible to automatically determine whether appropriate checks are made of the caller's identity or whether apporpriate appropriate permission requirements have been set in the manifest.
...