Insecure On-Device Model Storage

← AI/ML (OWASP LLM/GenAI Top 10)

insecure_ondevice_model_storage   MEDIUM

Description

On-device model file is unsigned/unencrypted and swappable.

How it works

The on-device model is stored unencrypted with no signature, so an attacker can read it or swap in a poisoned model and the app loads it with no integrity check. In the demo a legitimate model is saved, swapped, and the poisoned bytes load unchallenged. A hardened store verifies a signature over the model bytes before loading, so a swapped model is rejected.

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 AI/ML (OWASP LLM/GenAI Top 10) 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: r2, objection, frida, xxd · Android: adb, run-as · iOS: ifuse, afcclient.
2. Locate the target. From the home index, open Insecure On-Device Model Storage (insecure_ondevice_model_storage). 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. Send the crafted prompt / poisoned content to the in-app assistant and confirm the model obeys it - leaked system prompt/secret, an unconfirmed tool call, or attacker-controlled output.
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-0302, MASTG-TEST-0300 for the canonical procedure and remediation.

Tools (optional)

• r2
• objection
• frida
• xxd

Android

• adb
• run-as

iOS

• ifuse
• afcclient