CyberRota Analysis
AI-GeneratedApache Airflow's Yandex provider is vulnerable in multi-team mode, allowing a user from one team to access secrets belonging to another team by exploiting a fallback mechanism in the Yandex Lockbox secrets backend. This could lead to unauthorized access to sensitive credentials, posing a significant security risk in environments where team isolation is critical. Organizations utilizing Apache Airflow with multi-team configurations should prioritize upgrading to version 4.5.1 or later to mitigate this vulnerability.
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
The Yandex Lockbox secrets backend in Apache Airflow's Yandex provider resolved a team-scoped Connection or Variable id through the team-agnostic lookup when the team-scoped lookup missed. In a deployment running multi-team mode with this backend, a caller in one team could resolve a secret belonging to another team by supplying an id that spells out that team's namespace, 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-yandex 4.5.1 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.