CyberRota Analysis
AI-GeneratedThe Backfill API in Apache Airflow is vulnerable due to a discrepancy in how the `backfill_id` is parsed, allowing authenticated users with edit permissions on one DAG to manipulate backfills of other DAGs. This could lead to unauthorized access, including reading, pausing, and canceling backfills, as well as causing queued runs to fail. Organizations using Apache Airflow should prioritize upgrading to version 3.3.1 or later to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Apache Airflow's Backfill API authorized a request against a Dag id supplied by the caller whenever the `backfill_id` path segment failed to parse. The authorization dependency parsed it with `int()` while the route handler parsed it as pydantic's `NonNegativeInt`, which accepts values `int()` rejects (`1.0` coerces to `1`); FastAPI resolves dependencies before endpoint validation, so the two acted on different Dags. An authenticated user holding edit permission on any single Dag could therefore read, pause and cancel backfills belonging to any other Dag, including moving another Dag's queued runs to `failed`. No non-default configuration is required and backfill ids are sequential, so finding a target is trivial. Users are advised to upgrade to apache-airflow 3.3.1 or later, which parses the backfill id with the same type the routes declare.
Related CVEs
Other vulnerabilities affecting the same vendor(s)