Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-35798

Vulnerability in apache-airflow-providers-odbc (CVE-2023-35798)

Summary

Vulnerability in apache-airflow-providers-odbc (CVE-2023-35798). Risk of unauthorized operations or information disclosure. Exploitable via get_sqlalchemy_connection. Mitigation: upgrade to 4.0.0 or later.

Original description

The description as published by the source.

Input Validation vulnerability in Apache Software Foundation Apache Airflow ODBC Provider, Apache Software Foundation Apache Airflow MSSQL Provider.This vulnerability is considered low since it requires DAG code to use get_sqlalchemy_connection and someone with access to connection resources specifically updating the connection to exploit it.

This issue affects Apache Airflow ODBC Provider: before 4.0.0; Apache Airflow MSSQL Provider: before 3.4.1.

It is recommended to upgrade to a version that is not affected

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-35798 has been found in apache-airflow-providers-odbc.
Attackers can target a specific entry point like get_sqlalchemy_connection over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade apache-airflow-providers-odbc to 4.0.0 or later.
If unsure, ask your IT team or search "apache-airflow-providers-odbc CVE-2023-35798" on the vendor's site.

CVE-2023-35798 (apache-airflow-providers-odbc) — CWE-20
Attack vector: remote (network-reachable) / no user interaction
Attack surface: get_sqlalchemy_connection
Patched: 4.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-20) exists in apache-airflow-providers-odbc. Attackers reach the vulnerable code path via get_sqlalchemy_connection.

📍 Affected scope

Check the vendor advisory for the affected versions of apache-airflow-providers-odbc. Attack surface: get_sqlalchemy_connection.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.0.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'apache-airflow-providers-odbc' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'apache-airflow-providers-odbc' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で apache-airflow-providers-odbc を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade apache-airflow-providers-odbc to 4.0.0

    ステージング環境で 4.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI apache-airflow-providers-odbc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.0"}]}]
PyPI apache-airflow-providers-microsoft-mssql
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details