| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Apache Airflow up to 2.10.2 and classified as problematic. This impacts an unknown function of the component UI. Performing a manipulation of the argument sensitive results in log file. This vulnerability is known as CVE-2024-50378. No exploit is available. The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in Apache Airflow up to 2.10.2. This affects an unknown part of the component UI. The manipulation of the argument sensitive with an unknown input leads to a log file vulnerability. CWE is classifying the issue as CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. This is going to have an impact on confidentiality. The summary by CVE is:
Airflow versions before 2.10.3 have a vulnerability that allows authenticated users with audit log access to see sensitive values in audit logs which they should not see. When sensitive variables were set via airflow CLI, values of those variables appeared in the audit log and were stored unencrypted in the Airflow database. While this risk is limited to users with audit log access, it is recommended to upgrade to Airflow 2.10.3 or a later version, which addresses this issue. Users who previously used the CLI to set secret variables should manually delete entries with those variables from the log table.
The weakness was published by Saurabh Banawar. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-50378 since 10/23/2024. The exploitability is told to be easy. The exploitation requires an enhanced level of successful authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 2.10.3 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
- Product: https://github.com/apache/airflow/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.4VulDB Meta Temp Score: 2.3
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Log fileCWE: CWE-532 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Airflow 2.10.3
Timeline
10/23/2024 🔍11/08/2024 🔍
11/08/2024 🔍
07/11/2025 🔍
Sources
Vendor: apache.orgProduct: github.com
Advisory: github.com
Researcher: Saurabh Banawar
Status: Confirmed
CVE: CVE-2024-50378 (🔍)
GCVE (CVE): GCVE-0-2024-50378
GCVE (VulDB): GCVE-100-283545
Entry
Created: 11/08/2024 15:49Updated: 07/11/2025 09:41
Changes: 11/08/2024 15:49 (57), 07/11/2025 09:41 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

No comments yet. Languages: en.
Please log in to comment.