CVE-2024-28423
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAirflow-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAirflow-Diagrams v2.1.0 contains an arbitrary code execution vulnerability in cli.py where the unsafe_load function processes uploaded YAML files without sanitization. Attackers can exploit this by uploading a crafted YML file containing malicious YAML constructs that trigger arbitrary code execution during the deserialization process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Airflow-Diagrams is installedRun 'pip show airflow-diagrams' or check your Python environment for the airflow-diagrams packageAffected if The package is installed and version equals 2.1.0 exactly (or if version cannot be determined but the package is present)
-
Locate the cli.py file in the Airflow-Diagrams packageFind the cli.py file within the installed airflow-diagrams package directory (typically in site-packages/airflow_diagrams/)Affected if The cli.py file exists and is part of the installation
-
Inspect cli.py for unsafe_load usage with YAML processingOpen cli.py and search for 'unsafe_load' function calls used to parse YAML content, particularly in file upload handling codeAffected if cli.py contains unsafe_load (not safe_load) being used to deserialize YAML from uploaded files
-
Verify the file upload endpoint exists and accepts YAML filesCheck if there is an API endpoint or function in cli.py that accepts file uploads and passes them to yaml.unsafe_load for processingAffected if A file upload/upload endpoint exists that processes YAML files through unsafe_load
You are affected if Airflow-Diagrams version 2.1.0 is installed AND cli.py uses unsafe_load to process uploaded YAML files without validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace unsafe_load with PyYAML's safe_load or a restricted YAML parser, implement file upload validation to reject malicious YAML content, and consider sandboxing the YAML parsing operation.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28423 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data