Concurrent Workflow Exploitation
What you'll learn: How attackers use simultaneous workflow instances or parallel requests to create inconsistent application states and bypass business logic controls.
The Core Concept
Concurrent workflow exploitation occurs when an attacker initiates multiple instances of the same workflow simultaneously, or sends parallel requests that interfere with each other. This can create race conditions or logic flaws that wouldn't exist if workflows were processed sequentially.
Think of it like this: imagine a checkout system that checks "Do you have enough balance?" and then processes the purchase. If you submit two purchases at the exact same time, both checks might pass before either transaction deducts from your balance—allowing you to spend more than you have.
How Attackers Exploit This
Unlike simple race conditions that target a single operation, concurrent workflow exploitation targets entire multi-step processes:
- Multiple concurrent sessions: Opening several browser tabs and advancing through workflow steps in parallel
- Simultaneous form submissions: Submitting the same form multiple times before the first submission completes
- Parallel state transitions: Triggering state changes from multiple points simultaneously
Common vulnerable scenarios include:
- Discount code systems (applying the same code multiple times)
- Reservation systems (double-booking resources)
- Approval workflows (submitting while approval is pending)
- Cart checkout processes (manipulating quantities during payment)
Why Applications Are Vulnerable
Many applications assume workflows execute in isolation. They validate state at the beginning of a process but don't re-validate when critical operations occur—especially if multiple instances can run concurrently.
Key Takeaway: Concurrent workflow exploitation leverages parallel execution to create inconsistent application states by having multiple workflow instances interfere with each other, bypassing validations designed for sequential processing.