AI analysis
Apache DolphinScheduler before 3.4.3 has an improper authorization flaw in how sub-workflow tasks are handled. An authenticated user who lacks access to a target project can still reference and invoke a workflow in that project through a sub-workflow task, because the system does not check permission to execute the referenced workflow or to access its project. Successful exploitation bypasses project-level controls and can run unauthorized workflow tasks and reach resources or data available to the target workflow. Any deployment still on a version before 3.4.3 is affected. There is no known public proof of concept, the issue is not listed in CISA KEV, and exploitation in the wild is not known.
What to do: Upgrade Apache DolphinScheduler to 3.4.3 or later. Until then, restrict who can create or edit workflows that use sub-workflow tasks, and review workflow execution logs for tasks that invoked workflows in projects the caller was not authorized to access.
Affected
| Apache Software Foundation Apache DolphinScheduler | before 3.4.3 |
Estimated exposure
—No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description
An improper authorization vulnerability exists in the handling of sub-workflow tasks. An authenticated user who does not have permission to access a target project can reference and invoke a workflow belonging to that project through a sub-workflow task. The system does not properly verify whether the user has permission to execute the referenced workflow or access its project. As a result, the user can bypass project-level authorization controls and cause workflows in unauthorized projects to be executed. Successful exploitation may allow unauthorized execution of workflow tasks and access to the resources or data available to the target workflow. This issue affects Apache DolphinScheduler: before 3.4.3. Users are recommended to upgrade to version 3.4.3, which fixes the issue.