Dynamic Code Loading (Arbitrary Code Execution)

← Improper Platform Usage

dynamic_code_loading_rce   HARD

Description

Loads and executes a dex/module/plugin from an untrusted third-party app or external storage with no verification.

How it works

A plugin loader maps an untrusted module name to an executable op and runs it with no signature or allowlist check, so an attacker-supplied “wipe_data” module executes inside the app. This is a Dart simulation; the real exploit is native (DexClassLoader or dlopen loading an unsigned .dex/.so from an untrusted origin). A secure loader only runs allowlisted, signed modules.

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 Improper Platform Usage 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: Android: adb, jadx, apktool · iOS: ipsw, class-dump.
2. Locate the target. From the home index, open Dynamic Code Loading (Arbitrary Code Execution) (dynamic_code_loading_rce). 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. From a co-resident/attacker context (adb shell am start/drozer, or a crafted deep link / QR), send the untrusted input to the exported component or WebView and confirm the app performs the unsafe action (navigation, JS execution, file/URI access) with no validation.
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.

Tools (optional)

Android

• adb
• jadx
• apktool

iOS

• ipsw
• class-dump

Attack inputs

Payloads/artifacts you author for the on-device attack. The demo already ships and simulates these in-process (e.g. the malicious companion app / crafted intent is emulated inside the screen), so you only need to craft them to reproduce the exploit on a real device:

• malicious companion app