Since version 5.2.0, when using deferrable mode with the path of a Kubernetes configuration file for authentication, the Airflow worker serializes this configuration file as a dictionary and sends it to the triggerer by storing it in metadata without any encryption. Additionally, if used with an Airflow version between 2.3.0 and 2.6.0, the configuration dictionary will be logged as plain text in the triggerer service without masking. This allows anyone with access to the metadata or triggerer log to obtain the configuration file and use it to access the Kubernetes cluster. This behavior was changed in version 7.0.0, which stopped serializing the file contents and started providing the file path instead to read the contents into the trigger. Users are recommended to upgrade to version 7.0.0, which fixes this issue.
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
| Link | Tags |
|---|---|
| https://github.com/apache/airflow/pull/29498 | issue tracking patch |
| https://github.com/apache/airflow/pull/30110 | patch |
| https://github.com/apache/airflow/pull/36492 | issue tracking patch |
| https://lists.apache.org/thread/89x3q6lz5pykrkr1fkr04k4rfn9pvnv9 | mailing list vendor advisory |
| http://www.openwall.com/lists/oss-security/2024/01/24/3 | third party advisory mailing list |