The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider never applied the team scope when resolving Connections and Variables: the caller's `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team's Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NApache Airflow Providers Google
APPApache< 22.3.0
Powiązane podatności
Brak walidacji danych wejściowych w Apache Airflow Google Provider
Path Traversal w Apache Airflow Google Provider — zapis plików poza docelowym katalogiem
Apache Airflow providers-google's `ComputeEngineSSHHook` disables SSH host-key verification by default, exposi...
Improper Input Validation vulnerability in the Apache Airflow Google Provider. This issue affects Apache Airf...
Apache Tomcat: Path Equivalence prowadzący do RCE i ujawnienia danych