Concepts

Terms highlighted in blue in a level guide are added here as you reach each level. Concepts nest like folders: open one to see what's inside it.

9 of 91 concepts unlocked

  • Component

    1 inside

    A building block of an Android app. Instead of one big program, an app is a set of components that Android can start individually: screens, background workers, data providers and message receivers.

    Every component must be declared in the app's AndroidManifest.xml.

    Why it matters: Each component is a separate entry point into the app, so each one is a separate piece of attack surface.

    • A single screen of an app: the login screen, the settings screen, the notes list. Activities are started by sending them an intent.

  • The file where an app declares everything Android needs to know about it: its package name, permissions, and the full list of components, including which ones are exported and which intent filters they have.

    Why it matters: Reading the manifest is the first step of any attack: it tells you which doors the app has and which ones are open.

  • Intent

    4 inside

    A message one component sends to ask Android to do something: open a screen, share a photo, start a service. Apps use intents to talk to each other and to themselves.

    An intent says what to do (an action), may name who should do it, and can carry data in extras.

    Why it matters: If a component accepts intents from other apps, then anyone can craft the intent it receives. Everything inside the intent is attacker-controlled input.

    • An intent that doesn't name a specific app or component. It only describes what you want (usually with an action) and Android picks a component whose intent filter matches.

      The opposite is an explicit intent, which names the exact target component.

    • A string on an intent that names the thing to be done, for example android.intent.action.VIEW or a custom one like com.notesco.app.action.DEBUG_LOG.

      Why it matters: Custom actions are not secret. If you can read the manifest or the code, you can send the same action.

    • Key/value pairs attached to an intent, like message = "hello". The receiving component reads them to know what to work with.

      Why it matters: Extras are input like any other. If an app uses an extra without validating it, the sender decides what the app does with it, whether that is writing it to a log or fetching it as a URL.

    • A declaration in the manifest that tells Android which implicit intents (which actions) a component is willing to handle.

      On older Android versions a component with an intent filter is exported by default; newer versions require you to say so explicitly.

      Why it matters: A filter is an advertisement: it is how the system, and an attacker, finds the component.

  • A component marked android:exported="true" can be started by any other app on the device. If it is not exported, only the app itself (or apps sharing its user ID) can start it.

    Why it matters: Forgotten exported components are one of the most common Android bugs: a debug screen or helper exposed for convenience, never locked down again.