dbcve.org
Apache Airflow Providers DockerWeb server / proxy · Apache

CVE-2022-38362

HIGH · 8.8 CVSS v3.1 Published 2022-08-16
Fix available
A fix is available. Upgrade to 3.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Apache Airflow Docker's Provider prior to 3.0.0 shipped with an example DAG that was vulnerable to (authenticated) remote code exploit of code on the Airflow worker host.

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 · moderate confidence

Apache Airflow Docker provider versions prior to 3.0.0 shipped with a vulnerable example DAG that allows authenticated users to execute arbitrary code on the underlying Airflow worker host through improper input handling in the DAG.

MitigationRemove or update the vulnerable example DAG from the Airflow deployment, and upgrade the Docker provider to version 3.0.0 or later.

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
Apache Airflow Providers DockerWeb server / proxy
Affected:< 3.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Docker provider version
    Run 'pip show apache-airflow-providers-docker' or check via Airflow UI at Admin -> Providers -> docker
    Affected if Version displayed is lower than 3.0.0 or the package is not found (indicating an older version may be bundled)
  2. Locate Docker provider example DAGs
    Search for example DAG files in the Airflow DAGs folder, typically under $AIRFLOW_HOME/dags or in the provider's package directory at apache_airflow_providers_docker_example_dags
    Affected if Any DAG files originating from the Docker provider example collection exist in the deployment
  3. Inspect example DAG for unsafe input handling
    Open the example DAG file and examine operators that accept user-supplied parameters, looking for patterns where DAG run parameters or XCom values are passed to shell commands, bash_operator, or similar execution mechanisms without sanitization
    Affected if The example DAG contains code that passes run-time parameters directly to execution functions (such as BashOperator) without input validation
  4. Confirm example DAG is loaded by Airflow
    Check Airflow UI under DAGs view or run 'airflow dags list' to verify the example DAG from Docker provider is actively parsed and available
    Affected if The vulnerable example DAG appears in the DAGs list and has been loaded by the scheduler

The environment is affected if the Docker provider version is below 3.0.0 AND the vulnerable example DAG from that provider is present and loaded in the Airflow deployment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.0.0 or later
Fixed in 3.0.0
Interim mitigation

Remove or update the vulnerable example DAG from the Airflow deployment, and upgrade the Docker provider to version 3.0.0 or later.

Recommended fix High confidence

3.0.0

  1. Upgrade Apache Airflow Providers Docker package to version 3.0.0 or later using your package manager (e.g., pip install apache-airflow-providers-docker>=3.0.0)
  2. Restart the Airflow services to load the updated provider package
  3. Review and remove any deployed instances of the vulnerable example DAG (typically named docker_sample.py or similar in the example_dags directory)
  4. Verify the upgrade by checking the provider version in Airflow UI or via CLI: airflow providers list
  5. Ensure Airflow workers are restarted to pick up the patched code
Caveat Review release notes for 3.0.0 for any provider-specific changes; example DAGs may have been restructured or removed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apache Airflow Providers Docker Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38362 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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