CyberRota Analysis
AI-GeneratedThe vulnerability in Apache Airflow's Keycloak provider allows unauthenticated access to the token endpoint, enabling attackers to use valid credentials from any confidential client registered in the shared Keycloak realm to obtain signed session tokens for Airflow. This misconfiguration poses a significant risk, as it permits unauthorized access to resources based on the permissions of the compromised service account. Organizations utilizing Apache Airflow with Keycloak for authentication, particularly those sharing realms with other applications, should prioritize upgrading to version 0.10.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
Apache Airflow Keycloak provider: the unauthenticated token endpoint accepts a client-credentials grant for any confidential client registered in the Keycloak realm, not only the client configured for Airflow. No allowlist restricts which client ids may authenticate, so the credentials of an unrelated application that happens to share the realm are valid Airflow login credentials, and Airflow mints a signed session token for that application's service account. The endpoint also answers unauthenticated credential guesses against Keycloak under Airflow's identity. Affects deployments using the Keycloak auth manager whose realm is shared with other confidential clients. The attacker needs valid credentials for any one of those clients, not for Airflow. Resource authorization is still evaluated per subject, so the access gained is whatever that service account holds, plus any endpoint gated only on being authenticated. Users of apache-airflow-providers-keycloak are recommended to upgrade to version 0.10.0 or later, which accepts only the configured client on that grant.
Related CVEs
Other vulnerabilities affecting the same vendor(s)