# CVE-2019-0229: Apache Airflow vulnerable to CSRF Attacks

> Attackers can perform cross-site request forgery attacks against Apache Airflow webserver endpoints, potentially bypassing security controls.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w6j4-3gh2-9f5j, PYSEC-2019-215

## What is CVE-2019-0229?

CVE-2019-0229 is a high-severity vulnerability in Apache Airflow, published on 10 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A number of HTTP endpoints in the Airflow webserver (both RBAC and classic) did not have adequate protection and were vulnerable to cross-site request forgery attacks.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-0229?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-airflow` | PyPI | All versions | 1.10.3 |
| `apache-airflow` | PyPI | All versions | 1.10.3 |
| `apache-airflow` | PyPI | All versions | 1.10.3b1 |

Products: Apache Airflow.

## How do I fix CVE-2019-0229?

Upgrade apache-airflow to a fixed version for your release line: 1.10.3 or 1.10.3b1.

## Is CVE-2019-0229 being exploited?

There is no known exploitation of CVE-2019-0229 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-2019-0229 and fix it if it is affected.

What it is: CVE-2019-0229 is a high-severity vulnerability in Apache Airflow, published on 10 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-0229 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache-airflow (PyPI): affected all versions; fixed in 1.10.3
- apache-airflow (PyPI): affected all versions; fixed in 1.10.3
- apache-airflow (PyPI): affected all versions; fixed in 1.10.3b1

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-2019-0229/ (Markdown: https://insights.sbomify.com/CVE-2019-0229/index.md)
```

## Sources

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

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