CVE-2020-17511: Vulnerability in Apache Airflow

airflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2020-17511: In Airflow versions prior to 1.10.13, when creating a user using airflow CLI, the password gets logged in plain text in the Log table in Airflow Metadatase. Affects airflow versions < 1.10.13. Fixed in 1.10.13. How to fix ↓

Also tracked for

The same CVE-2020-17511 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache Airflow is an open-source platform used for orchestrating and scheduling workflows. It allows users to define, schedule, and monitor complex workflows as directed acyclic graphs (DAGs). Airflow CLI is a command-line interface provided by Airflow for managing users and connections. The vulnerability in Airflow versions prior to 1.10.13 allows the password to be logged in plain text in the Log table in Airflow Metadata when creating a user using the CLI or when creating a Connection with a password field.

Vulnerability Detail

The vulnerability (CVE-2020-17511) arises from the insecure logging of passwords in plain text. When a user is created using the Airflow CLI or a Connection is created with a password field, the password is stored in the Log table in Airflow Metadata without proper encryption. This can lead to unauthorized access to sensitive information if an attacker gains access to the logs or the database. The impact of this vulnerability is medium, as it requires local access to the logs or the database to exploit it.

How To Fix

Minimum fixed version

1.10.13

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. The recommended solution is to upgrade to the fixed version of Airflow.

Conclusion

In conclusion, the vulnerability (CVE-2020-17511) in Apache Airflow allows passwords to be logged in plain text in the Log table in Airflow Metadata. This can lead to unauthorized access to sensitive information if an attacker gains access to the logs or the database. It is recommended to upgrade to Airflow version 1.10.13 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for airflow →

Share this vulnerability

FAQ

Apache Airflow is an open-source platform used for orchestrating and scheduling workflows. It allows users to define, schedule, and monitor complex workflows as directed acyclic graphs (DAGs).

The impact of this vulnerability is medium, as it requires local access to the logs or the database to exploit it. If an attacker gains access to the logs or the database, they can retrieve passwords in plain text.

To fix this vulnerability, it is recommended to upgrade to Airflow version 1.10.13 or later. This version includes a fix for the insecure logging of passwords.

There is no specific workaround provided for this vulnerability. The recommended solution is to upgrade to the fixed version of Airflow.

You can find more information about this vulnerability in the CVE-2020-17511 entry or the provided source link.

Related vulnerabilities

Recent vulnerabilities recorded for airflow.

How To Fix

Minimum fixed version

1.10.13

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback