UnsafeIntentLaunchViolation Class

Definition

[Android.Runtime.Register("android/os/strictmode/UnsafeIntentLaunchViolation", ApiSince=31, DoNotGenerateAcw=true)]
public sealed class UnsafeIntentLaunchViolation : Android.OS.Strictmode.Violation

[<Android.Runtime.Register("android/os/strictmode/UnsafeIntentLaunchViolation", ApiSince=31, DoNotGenerateAcw=true)>]
type UnsafeIntentLaunchViolation = class
    inherit Violation

Inheritance

Exception

JavaException

Throwable

Violation

UnsafeIntentLaunchViolation

Attributes

RegisterAttribute

Remarks

Violation raised when your app launches an Intent which originated from outside your app.

Violations may indicate security vulnerabilities in the design of your app, where a malicious app could trick you into granting Uri permissions or launching unexported components. Here are some typical design patterns that can be used to safely resolve these violations: <ul> <li>The ideal approach is to migrate to using a PendingIntent, which ensures that your launch is performed using the identity of the original creator, completely avoiding the security issues described above. <li>If using a PendingIntent isn't feasible, an alternative approach is to create a brand new Intent and carefully copy only specific values from the original Intent after careful validation. </ul>

Note that this <em>may</em> detect false-positives if your app sends itself an Intent which is first routed through the OS, such as using Intent#createChooser. In these cases, careful inspection is required to determine if the return point into your app is appropriately protected with a signature permission or marked as unexported. If the return point is not protected, your app is likely vulnerable to malicious apps.

Java documentation for android.os.strictmode.UnsafeIntentLaunchViolation.

Portions of this page are modifications based on work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.