# CVE-2023-35005: Apache Airflow: Information disclosure on configuration view

> Attackers can view potentially sensitive configuration values in the UI if the expose_config setting is enabled.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2023
- **Updated:** 9 Oct 2024
- **Also known as:** BIT-airflow-2023-35005, GHSA-mjff-wv85-hmcj, PYSEC-2023-89

## What is CVE-2023-35005?

CVE-2023-35005 is a medium-severity vulnerability in Apache Airflow, published on 19 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Apache Airflow, some potentially sensitive values were being shown to the user in certain situations.

This vulnerability is mitigated by the fact configuration is not shown in the UI by default (only if `[webserver] expose_config` is set to `non-sensitive-only`), and not all uncensored values are actually sentitive.

This issue affects Apache Airflow: from 2.5.0 before 2.6.2. Users are recommended to update to version 2.6.2 or later.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-35005?

4 open source packages ship an affected version, including apache-airflow and airflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-airflow` | PyPI | From 2.5.0 | 2.6.2 |
| `apache-airflow` | PyPI | From 2.5.0 | 2.6.2rc1 |
| `apache-airflow` | PyPI | From 2.5.0 | 2.6.2rc1 |
| `airflow` | Bitnami | From 2.5.0 | 2.6.2 |

Products: Apache Airflow.

## How do I fix CVE-2023-35005?

Upgrade apache-airflow to a fixed version for your release line: 2.6.2 or 2.6.2rc1.

## Is CVE-2023-35005 being exploited?

There is no known exploitation of CVE-2023-35005 in the wild and no public exploit code.

## Other vulnerabilities in Apache Airflow

- [CVE-2020-13927](https://insights.sbomify.com/CVE-2020-13927/): Apache Airflow's Experimental API Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-11978](https://insights.sbomify.com/CVE-2020-11978/): Apache Airflow Command Injection (high 8.8, exploited in the wild)
- [CVE-2026-33264](https://insights.sbomify.com/CVE-2026-33264/): Apache Airflow: DAG author RCE on webserver via unrestricted import_string() in BaseSerialization.deserialize() (critical 9.8)
- [CVE-2023-25754](https://insights.sbomify.com/CVE-2023-25754/): Apache Airflow: Privilege escalation using airflow logs (critical 9.8)
- [CVE-2023-22884](https://insights.sbomify.com/CVE-2023-22884/): Apache Airflow, Apache Airflow MySQL Provider: Arbitrary file read via MySQL provider in Apache Airflow (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35005 and fix it if it is affected.

What it is: CVE-2023-35005 is a medium-severity vulnerability in Apache Airflow, published on 19 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-35005 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache-airflow (PyPI): affected from 2.5.0; fixed in 2.6.2
- apache-airflow (PyPI): affected from 2.5.0; fixed in 2.6.2rc1
- apache-airflow (PyPI): affected from 2.5.0; fixed in 2.6.2rc1
- airflow (Bitnami): affected from 2.5.0; fixed in 2.6.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-35005/ (Markdown: https://insights.sbomify.com/CVE-2023-35005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-35005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-35005
- OSV: https://osv.dev/vulnerability/CVE-2023-35005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-35005/
Summaries are generated and may contain mistakes; the official description above is the record.