Apache Airflow Providers Apache HiveWeb server / proxy · Apache

CVE-2023-37415

HIGH · 8.8 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to 6.1.2 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 Apache Hive Provider. Patching on top of CVE-2023-35797 Before 6.1.2 the proxy_user option can also inject semicolon. This issue affects Apache Airflow Apache Hive Provider: before 6.1.2. It is recommended updating provider version to 6.1.2 in order to avoid this vulnerability.

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

Improper input validation in Apache Airflow Hive Provider allows semicolon injection via the proxy_user option, potentially enabling command injection. This is a follow-up patch to CVE-2023-35797, indicating the original fix was incomplete.

MitigationUpdate the Apache Airflow Hive Provider to version 6.1.2 or later to remediate this vulnerability.

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 Apache HiveWeb server / proxy
Affected:< 6.1.2

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. Identify if Hive Provider is installed
    Run `pip show apache-airflow-providers-hive` or check your requirements/pip list for the `apache-airflow-providers-hive` package
    Affected if The package is not installed or the version cannot be determined
  2. Check installed Hive Provider version
    Run `pip show apache-airflow-providers-hive` and look for the Version field, or run `pip list | grep airflow-providers-hive`
    Affected if The installed version is lower than 6.1.2 (e.g., 6.1.1, 6.1.0, 5.x.x)
  3. Identify use of proxy_user configuration
    Search Airflow DAGs, configuration files, and Hive hook connections for any use of the `proxy_user` parameter in Hive-related operators, hooks, or connections
    Affected if The proxy_user parameter is being used to pass user-supplied or external input without sanitization

You are affected if the apache-airflow-providers-hive package is installed with a version lower than 6.1.2 AND the proxy_user option in your Hive connections or operators accepts unsanitized external input.

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

Update the Apache Airflow Hive Provider to version 6.1.2 or later to remediate this vulnerability.

Recommended fix High confidence

6.1.2

  1. Identify the current version of apache-airflow-providers-hive by running: pip show apache-airflow-providers-hive
  2. Upgrade the package to version 6.1.2 or later using: pip install --upgrade apache-airflow-providers-hive>=6.1.2
  3. Verify the installation was successful by checking the installed version: pip show apache-airflow-providers-hive

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

Fix this in Apache Airflow Providers Apache Hive Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37415 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