Apache Airflow: Creating DagRuns didn't respect Dag-level permissions in the Webserver
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Airflow | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
Vendor Workaround
This is a very low severity CVE and admins can mitigate this issue by removing the global "can_create" permissions on DagRun for Airflow versions >=2.0.0,<2.2.0 and 1.10.x versions that have set `rbac=True` in config.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-0007 | In Apache Airflow prior to 2.2.0. This CVE applies to a specific case where a User who has \"can_create\" permissions on DAG Runs can create Dag Runs for dags that they don't have \"edit\" permissions for. |
Github GHSA |
GHSA-4jh2-3c85-q67h | Improper Privilege Management in apache-airflow |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.8% (1.766% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.