# CVE-2024-28423: File upload in n/a

> Attackers can execute arbitrary code by uploading a crafted YML file via the unsafe_load function in Airflow-Diagrams.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2024
- **Updated:** 27 Aug 2024
- **Also known as:** GHSA-2qqg-5pcx-4jv3, PYSEC-2024-263

## What is CVE-2024-28423?

CVE-2024-28423 is a critical vulnerability in n/a, published on 14 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Airflow-Diagrams v2.1.0 was discovered to contain an arbitrary file upload vulnerability in the unsafe_load function at cli.py. This vulnerability allows attackers to execute arbitrary code via uploading a crafted YML file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-28423?

1 open source package ship an affected version, including airflow-diagrams. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `airflow-diagrams` | PyPI | All versions to 2.1.0 | None |

Products: Feluelle Airflow-Diagrams.

## How do I fix CVE-2024-28423?

No fix has been published for CVE-2024-28423 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-28423 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28423 and fix it if it is affected.

What it is: CVE-2024-28423 is a critical vulnerability in n/a, published on 14 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28423 in the wild and no public exploit code.

Affected packages and fixed versions:
- airflow-diagrams (PyPI): affected all versions up to 2.1.0; no fix listed

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

## Sources

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

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