First published: Wed Jan 24 2024(Updated: )
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.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/apache-airflow-providers-cncf-kubernetes | >=5.2.0<7.0.0 | 7.0.0 |
pip/apache-airflow | >=2.3.0<2.6.1 | 2.6.1 |
Apache Airflow | >=2.3.0<2.6.1 | |
Apache Airflow | >=5.2.0<7.0.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2023-51702 is considered high due to the potential exposure of sensitive configuration information.
To fix CVE-2023-51702, upgrade the apache-airflow-providers-cncf-kubernetes package to version 7.0.0 or later and the apache-airflow package to version 2.6.1 or later.
CVE-2023-51702 affects Apache Airflow versions between 2.3.0 and 2.6.1 and apache-airflow-providers-cncf-kubernetes versions between 5.2.0 and 7.0.0.
The impact of CVE-2023-51702 includes the potential unauthorized access to sensitive Kubernetes configuration data due to lack of encryption.
No, CVE-2023-51702 is not classified as a remote code execution vulnerability but rather as a confidential information exposure vulnerability.