Skip to content

MASWE-0066: Insecure Intents

Content in BETA

This content is in beta and still under active development, so it is subject to change any time (e.g. structure, IDs, content, URLs, etc.).

Send Feedback

Draft Weakness

This weakness hasn't been created yet and it's in draft. But you can check its status or start working on it yourself. If the issue has not yet been assigned, you can request to be assigned to it and submit a PR with the new content for that weakness by following our guidelines.

Check our GitHub Issues for MASWE-0066

Initial Description or Hints

e.g. calling startActivity, startService, sendBroadcast, or setResult on untrusted Intents without validating or sanitizing these Intents. Using an implicit intent to start a service is a security hazard, because you can't be certain what service will respond to the intent and the user can't see which service starts. e.g. mutable pending intents (not using FLAG_IMMUTABLE), replaying pending intents (not using FLAG_ONE_SHOT)

Relevant Topics

  • Insecure Intent Redirection
  • Insecure Implicit Intents
  • Insecure Pending Intents (Mutable, Replaying)


MASTG v1 Coverage

No MASTG v1 tests are related to this weakness.