CVE-2024-56373: Apache Airflow: SSTI to Code Execution in Airflow through Shared DB Information
DAG Author (who already has quite a lot of permissions) could manipulate database of Airflow 2 in the way to execute arbitrary code in the web-server context, which they should normally not be able to do, leading to potentially remote code execution in the context of web-server (server-side) as a result of a user viewing historical task information.
The functionality responsible for that (log template history) has been disabled by default in 2.11.1 and users should upgrade to Airflow 3 if they want to continue to use log template history. They can also manually modify historical log file names if they want to see historical logs that were generated before the last log template change.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56373?
CVE-2024-56373 has a high severity as it allows for arbitrary code execution through Server-Side Template Injection.
How do I fix CVE-2024-56373?
To fix CVE-2024-56373, upgrade Apache Airflow to version 2.11.1 or greater.
Who is affected by CVE-2024-56373?
Users of Apache Airflow versions prior to 2.11.1 and from 3.0.0 onwards are affected by CVE-2024-56373.
What kind of attack does CVE-2024-56373 enable?
CVE-2024-56373 enables an attacker to execute arbitrary code within the Airflow web-server context.
What should I do if I cannot upgrade to mitigate CVE-2024-56373?
If you cannot upgrade, limit the permissions of DAG authors and implement strong access controls to reduce the risk.