Improper Signature Verification (payload not bound)

← Insufficient Cryptography

improper_signature_verification   HARD

Description

An RSA-SHA256 signed update blob is accepted because the app only checks a signature is present and well-formed, never that it binds to the payload; an attacker keeps the original signature, swaps the payload, and the tampered update is accepted while a correct verification rejects it.

How it works

An update blob ships with a real RSA-SHA256 signature. The app accepts the update because a signature is present and well-formed, but never verifies that it binds to the payload. An attacker keeps the original signature, swaps the payload, and the update is accepted, while a correct verification against the payload rejects it.

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 Insufficient Cryptography 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: frida, r2, openssl.
2. Locate the target. From the home index, open Improper Signature Verification (payload not bound) (improper_signature_verification). 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. Capture the algorithm/key/IV the module uses (the evidence panel prints it), then reproduce the weakness offline - e.g. recompute the digest, brute the short key, or decrypt a captured blob - to show the protection is ineffective.
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)

• frida
• r2
• openssl

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:

• tampered payload