AirflowApplication · Apache
CVE-2022-24288
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 · uneditedIn Apache Airflow, prior to version 2.2.4, some example DAGs did not properly sanitize user-provided params, making them susceptible to OS Command Injection from the web UI.
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 confidenceApache Airflow versions prior to 2.2.4 contain example DAGs that fail to sanitize user-supplied parameters, allowing authenticated web UI users to inject arbitrary OS commands through those parameters. The vulnerability stems from improper input handling in example DAG code that directly uses user params in shell execution contexts.
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
AirflowApplication
< 2.2.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check installed Apache Airflow versionRun 'pip show apache-airflow' or check your package manager for the installed airflow versionAffected if Version is lower than 2.2.4 (e.g., 2.2.3, 2.2.0, 2.1.x, 2.0.x)
-
Locate example DAGs directoryFind the airflow example_dags folder - typically at $AIRFLOW_HOME/dags or within the airflow package (search for 'example_dags' directory)Affected if Example DAGs directory exists and contains DAG files
-
Identify vulnerable example DAGsSearch example DAG files for patterns that execute shell commands using user-provided parameters (look for 'bash_command', 'sh', or 'subprocess' calls with Jinja-templated variables like '{{ params.xxx }}')Affected if Any example DAG files contain shell execution using unvalidated user params in templates
-
Check if example DAGs are enabled in AirflowAccess Airflow web UI (port 8080 by default), navigate to DAGs view, and check if any example DAGs are toggled 'On' (active)Affected if Example DAGs are present and enabled/loaded in the scheduler
You are affected if running Apache Airflow version less than 2.2.4 AND example DAGs are installed and enabled, as the vulnerability requires both the vulnerable version and the presence of the example DAG code that uses unsanitized user parameters in shell execution.
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.
dbcve · scoped2.2.4
Upgrade Apache Airflow to version 2.2.4 or later, which contains fixes for the unsanitized example DAGs. If immediate upgrade is not feasible, remove or disable the vulnerable example DAGs and implement proper input validation/sanitization for any custom DAGs that accept user parameters.
Apache Airflow 2.2.4 or later
- 1. Back up your current Airflow environment (database, DAGs, and configuration)
- 2. Upgrade Apache Airflow to version 2.2.4 or later using your package manager (e.g., pip install apache-airflow==2.2.4)
- 3. Run any necessary database migrations after upgrade
- 4. Verify the upgrade was successful by checking the Airflow version
- 5. Test that example DAGs function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Airflow
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24288 — 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-2022-24288 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