Exported Android component exposes a protected operation
An externally reachable activity, service or receiver performs work that its caller is not entitled to request.
Candidate CWE: CWE-926
Test hypothesis#
Record the intended app action, then repeat one harmless seeded operation from an ordinary companion app without the required permission. Compare with an explicitly authorized caller.
Evidence required#
Package/build/API level, resolved export and permission state, companion identity, exact intent, expected denial and protected result.
Rule out false positives#
Exported status or opening a public screen is insufficient. ADB-only access or privileged caller setup does not establish ordinary-app reachability.
Playbook and command references#
- Android components, intents and deep links — Trace ordinary-app inputs through exported components, URI grants and links to one protected operation.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.