auditing-android-component-exposurelisted

# Auditing Android component exposure: what another app on the device can reach and drive An Android component is only an attack surface if another app can reach it, so this audit is a resolution of the export state and the permission gate, not a scan of component names. A component is exported when a flag says so or an intent filter makes it so by default, and it is exposed only when no permission of a strong enough protection level gates the caller. The bug is a sensitive component another installed app can invoke, and then trust the caller's intent extras to do something it should not. You audit it by resolving, per component, whether it is reachable across the app boundary and what it does with an attacker's intent. Stay on component reachability and inbound-intent handling; when the exposure is a URL the component hands to a WebView, that is the deep-link skill's seam, cross-referenced below. ## When to use - You are reviewing an Android manifest and the activities, services, receivers, or providers it declares. - A component sets an export flag or an intent filter, or handles intent extras for a sensitive action. - You want to know which components another app on the device can actually reach and drive. ## Scope check Audit only apps you own or are authorized to assess, and exercise a component only on a device or emulator in scope, invoking an exported component drives real app state. Adjudicate on the manifest and the handler. If you can't name the authorization,