Debuggable Release Build

← Code Quality & Build Config

debuggable_release_build   EASY

Description

Release build ships with debuggable=true / debug flags left on.

How it works

A build that ships debuggable (Android android:debuggable=“true” / iOS get-task-allow entitlement) lets anyone attach a debugger to inspect memory, set breakpoints, and dump secrets at runtime. This screen reports the real build mode (from kReleaseMode) rather than a hardcoded claim: a debug or profile build is debuggable, so attaching a debugger works.

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 Code Quality & Build Config 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: MobSF · Android: aapt, jadx, adb, apktool · iOS: ideviceinstaller, codesign, ipsw.
2. Locate the target. From the home index, open Debuggable Release Build (debuggable_release_build). 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. Statically inspect the shipped artifact (jadx, strings, nm, aapt dump badging) and confirm the build/quality weakness is present in the release binary.
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-0226, MASTG-TEST-0261 for the canonical procedure and remediation.

Tools (optional)

• MobSF

Android

• aapt
• jadx
• adb
• apktool

iOS

• ideviceinstaller
• codesign
• ipsw