Missing Consent Before Data Access

← Privacy (OWASP Mobile M6)

missing_consent_before_data_access   EASY

CategoryPrivacy (OWASP Mobile M6)
OWASP Mobile (2024)M6
MASVSMASVS-PRIVACY-1MASVS-PRIVACY-2
MASWEMASWE-0078
MASTG (v2 tests)iOSMASTG-TEST-0360AndroidMASTG-TEST-0256
MASTG demosiOSMASTG-DEMO-0126AndroidNone published
CWECWE-359
PlatformAndroidiOS

Description

Accesses location/contacts/photos with no consent screen.

How it works

The app reads contacts, precise location, and the photo library without ever showing a consent screen or explaining why, then writes the harvested data to a real on-disk file. Sensitive data access must be gated on informed, purpose-specific consent.

How to exercise it. DVMA is the harness - open this module from the home index and tap the demo action. The screen ships the malicious input and simulates the attacker (e.g. the companion app, crafted intent, or scanned payload) in-process, and the evidence panel prints the proof. The Tools (optional) and Attack inputs below are only needed to reproduce the exploit end-to-end on a real device.

Exploit steps

  1. Set up. Build DVMA with a flavor that enables the Privacy (OWASP Mobile M6) category (e.g. --dart-define-from-file=config/flavors/dev.json) and run on an emulator/simulator you control. The demo needs no external tooling; for the optional on-device reproduction the relevant tools are: mitmproxy, Burp Suite, frida.
  2. Locate the target. From the home index, open Missing Consent Before Data Access (missing_consent_before_data_access). The How it works section above describes this module’s specific weakness; the screen states the intended-secure behavior and exposes the vulnerable action.
  3. Exploit. Trigger the data-access/telemetry path and confirm sensitive data is collected, transmitted, or associated without the required consent / transparency prompt.
  4. Observe the evidence. Trigger the vulnerable action and read the evidence panel - it prints the concrete proof (leaked value, accepted replay, executed payload, or unauthorized result).
  5. Contrast with the secure path. Run the module’s secure/hardened action (where provided) and confirm the same attack is rejected - this is what a correct implementation should do.
  6. Map it back. Cross-reference the MASTG v2 test(s) MASTG-TEST-0360, MASTG-TEST-0256 for the canonical procedure and remediation.

Tools (optional)