Weak / No Password Policy

← Insecure Authentication / Authorization

weak_password_policy   EASY

CategoryInsecure Authentication / Authorization
OWASP Mobile (2024)M3
MASVSMASVS-AUTH-1
MASWEMASWE-0018
CWECWE-521
PlatformAndroidiOS

Description

Accepts single-character passwords; no complexity or length checks.

How it works

The registration form accepts any non-empty password, including a single character or “123456”. There are no length, complexity, or breached-password checks, so accounts are trivially brute-forceable.

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 Insecure Authentication / Authorization 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: Burp Suite, mitmproxy.
  2. Locate the target. From the home index, open Weak / No Password Policy (weak_password_policy). 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. Drive the authentication/authorization path, capture the token / assertion / decision, then replay or tamper with it (mitmproxy, a WebAuthn test harness, or by editing the value) and confirm the server-side check accepts the manipulated request.
  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)