CyberRota Analysis
AI-GeneratedThe Apache Airflow Git provider is vulnerable due to its default configuration of `StrictHostKeyChecking=no`, which allows for SSH host-key verification to be bypassed. This vulnerability enables attackers to perform man-in-the-middle attacks, potentially capturing sensitive SSH deploy keys or injecting malicious content into repositories. Organizations using Apache Airflow with Git for deployments should prioritize upgrading to version 0.4.1 or later and ensure proper host key verification is configured 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 Apache Airflow Git provider runs its git-over-SSH operations with `StrictHostKeyChecking=no` by default, disabling SSH host-key verification. An attacker who can intercept the network path between an Airflow worker and the Git server can impersonate the server (man-in-the-middle), capturing the SSH deploy key or injecting malicious repository content. Deployments that use the Git DAG bundle or Git provider to clone over SSH with a deploy key are affected. The fix changes the default to verify host keys; upgrade to apache-airflow-providers-git `0.4.1` or later and configure a `known_hosts` file.
Related CVEs
Other vulnerabilities affecting the same vendor(s)