← Back
CVE-2024-36105
Vulnerability in dbt-core (CVE-2024-36105)
Summary
vulnerability in dbt-core (CVE-2024-36105). Risk of unauthorized operations or information disclosure. Exploitable via ``INADDR_ANY``. Mitigation: upgrade to `1.8.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-36105** has been found in dbt-core.
Attackers can target a specific entry point like ``INADDR_ANY`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade dbt-core to **1.8.1** or later.
If unsure, ask your IT team or search "dbt-core CVE-2024-36105" on the vendor's site.
CVE-2024-36105 (dbt-core) — CWE-1327 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `INADDR_ANY` / `IN6ADDR_ANY` / `netstat`
Patched: `1.8.1` — 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-1327) exists in dbt-core. Attackers reach the vulnerable code path via ``INADDR_ANY`` without authentication.
📍 Affected scope
dbt-core — . Attack surface: `INADDR_ANY` / `IN6ADDR_ANY` / `netstat`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.8.1**.
🛡️ 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 'dbt-core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dbt-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `dbt-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade dbt-core to 1.8.1ステージング環境で 1.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
dbt-core
[{"type":"ECOSYSTEM","events":[{"introduced":"1.8.0"},{"fixed":"1.8.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-36105
- advisory https://github.com/advisories/GHSA-pmrx-695r-4349
- package https://github.com/dbt-labs/dbt-core
- package https://pypi.org/project/dbt-core
- web https://github.com/dbt-labs/dbt-core/security/advisories/GHSA-pmrx-695r-4349
- web https://github.com/dbt-labs/dbt-core/issues/10209
- web https://github.com/dbt-labs/dbt-core/pull/10208
- web https://github.com/dbt-labs/dbt-core/commit/0c08d7a19ad1740be3cb0b2e6d9d64f6537176f7
- web https://cwe.mitre.org/data/definitions/1327.html
- web https://docs.python.org/3/library/socket.html#socket-families
- web https://docs.securesauce.dev/rules/PY030
- web https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/task/docs/serve.py#L23C38-L23C39
- web https://github.com/dbt-labs/dbt-core/releases/tag/v1.6.15
- web https://github.com/dbt-labs/dbt-core/releases/tag/v1.7.15
- web https://github.com/dbt-labs/dbt-core/releases/tag/v1.8.1