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

CVE-2023-22886

HIGH · 8.8 CVSS v3.1 Published 2023-06-29
Fix available
A fix is available. Upgrade to 4.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
Improper Input Validation vulnerability in Apache Software Foundation Apache Airflow JDBC Provider. Airflow JDBC Provider Connection’s [Connection URL] parameters had no restrictions, which made it possible to implement RCE attacks via different type JDBC drivers, obtain airflow server permission. This issue affects Apache Airflow JDBC Provider: before 4.0.0.

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 confidence

The Apache Airflow JDBC Provider before version 4.0.0 lacks input validation on Connection URL parameters, allowing attackers to craft malicious JDBC connection strings that can load arbitrary JDBC drivers and achieve remote code execution on the Airflow server with the permissions of the airflow service account.

MitigationUpgrade Apache Airflow JDBC Provider to version 4.0.0 or later which implements proper input validation on connection URL parameters. If immediate upgrade is not possible, restrict JDBC connection configuration permissions to trusted administrators only.

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 JdbcWeb server / proxy
Affected:< 4.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 if JDBC Provider is installed
    Run 'pip show apache-airflow-providers-jdbc' or check your requirements/pip list for package 'apache-airflow-providers-jdbc'
    Affected if The package is installed and its version is below 4.0.0
  2. Verify JDBC connection configurations exist
    Check Airflow metadata database for connections in 'connections' table where 'conn_type' is 'jdbc', or inspect your CSV/JSON connection files for entries with 'jdbc' prefix
    Affected if JDBC connections are defined in your Airflow environment
  3. Inspect JDBC connection URL parameters
    Review your JDBC connection URLs for the presence of parameters like 'driver', 'driver_path', 'classpath', or any URL parameters that could load arbitrary Java classes
    Affected if Connection URLs contain dynamic driver loading parameters or accept arbitrary URL parameters without validation
  4. Check user access to connection configuration
    Review Airflow RBAC roles and permissions to determine which users or roles can create/modify connections, or check if non-admin users have access to the '/connection' API endpoints
    Affected if Users beyond trusted administrators can create or modify JDBC connections

You are affected if apache-airflow-providers-jdbc version is below 4.0.0 AND your Airflow deployment has JDBC connections configured with parameters that allow arbitrary driver/class loading accessible to non-admin users.

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 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Upgrade Apache Airflow JDBC Provider to version 4.0.0 or later which implements proper input validation on connection URL parameters. If immediate upgrade is not possible, restrict JDBC connection configuration permissions to trusted administrators only.

Recommended fix High confidence

4.0.0

  1. Upgrade Apache Airflow Providers Jdbc package to version 4.0.0 or later using your package manager (e.g., pip install apache-airflow-providers-jdbc==4.0.0)
  2. Verify the upgrade was successful by checking the installed version
  3. Restart any Airflow services to ensure the new provider version is loaded

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

Fix this in Apache Airflow Providers Jdbc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22886 — 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-2023-22886 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