Executive Summary

This vulnerability exists in Apache Airflow versions 3.1.0 through 3.1.7 in the /ui/dependencies endpoint of its REST API.

The endpoint returns the full Directed Acyclic Graph (DAG) dependency graph without filtering based on user authorization.

As a result, an authenticated user who only has permission to view DAG Dependencies can enumerate DAGs they are not authorized to access.

The issue was fixed in Apache Airflow 3.1.8 by adding authorization checks to ensure that only DAGs the user is authorized to view are returned.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized information disclosure by allowing users to see DAG dependency graphs they should not have access to.

Such unauthorized enumeration of DAGs could expose sensitive workflow structures or business logic embedded in the DAGs.

This exposure may increase the risk of further attacks or misuse of the system by revealing internal process dependencies.

Useful 0 Not Useful 0

Compliance Impact

I don't know

Useful 0 Not Useful 0

Detection Guidance

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by attempting to access the /ui/dependencies endpoint of Apache Airflow versions 3.1.0 through 3.1.7 with an authenticated user who has only DAG Dependencies permission. If the endpoint returns the full DAG dependency graph without filtering by authorized DAG IDs, the system is vulnerable.'}, {'type': 'paragraph', 'content': 'A practical approach is to use an HTTP client (such as curl) to send an authenticated request to the /ui/dependencies endpoint and observe if unauthorized DAG information is returned.'}, {'type': 'list_item', 'content': 'curl -H "Authorization: Bearer <token>" https://<airflow-server>/ui/dependencies'}, {'type': 'list_item', 'content': 'Check the response for DAGs that the authenticated user should not have access to.'}] [1]

Useful 0 Not Useful 0

Mitigation Strategies

The recommended immediate step is to upgrade Apache Airflow to version 3.1.8 or later, where this issue has been resolved by enforcing authorization filtering on the /ui/dependencies endpoint.

Until the upgrade can be performed, restrict access to the /ui/dependencies endpoint to only fully trusted users or disable the endpoint if possible to prevent unauthorized DAG enumeration.

Useful 0 Not Useful 0