CyberRota Analysis
AI-GeneratedThe Azure Key Vault secrets backend in Apache Airflow's Microsoft Azure provider is vulnerable in multi-team mode, allowing a user from one team to access secrets belonging to another team by manipulating the connection or variable ID. This could lead to unauthorized credential exposure, potentially compromising sensitive data across teams. Organizations utilizing Apache Airflow in multi-team environments should prioritize upgrading to version 14.1.0 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
The Azure Key Vault secrets backend in Apache Airflow's Microsoft Azure 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-microsoft-azure 14.1.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.