Problem
The workflow engine's HTTP dispatcher plugin executes POST requests to URLs defined within task configurations without egress restrictions or URL validation. If a task template specifies an arbitrary URL, the service will attempt to dispatch payload data (including user/task information) to that target.
Proposed Solution
- Route all outbound requests from workflow plugins through a central, secure HTTP client helper.
- Enforce validation on dispatch targets (requiring HTTPS and blocking private/link-local IP ranges).
- Implement strict re-validation policies on HTTP redirects (
CheckRedirect).
Alternatives
No response
Problem
The workflow engine's HTTP dispatcher plugin executes POST requests to URLs defined within task configurations without egress restrictions or URL validation. If a task template specifies an arbitrary URL, the service will attempt to dispatch payload data (including user/task information) to that target.
Proposed Solution
CheckRedirect).Alternatives
No response