# CVE-2024-36105: dbt allows Binding to an Unrestricted IP Address via socketsocket

> dbt-core exposed documentation servers on all network interfaces, allowing unauthorized remote access to data on unsecured networks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-pmrx-695r-4349, PYSEC-2026-1292

## What is CVE-2024-36105?

CVE-2024-36105 is a medium-severity vulnerability in dbt-labs dbt-core, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. Prior to versions 1.6.15, 1.7.15, and 1.8.1, Binding to `INADDR_ANY (0.0.0.0)` or `IN6ADDR_ANY (::)` exposes an application on all network interfaces, increasing the risk of unauthorized access. As stated in the Python docs, a special form for address is accepted instead of a host address: `''` represents `INADDR_ANY`, equivalent to `"0.0.0.0"`. On systems with IPv6, '' represents `IN6ADDR_ANY`, which is equivalent to `"::"`. A user who serves docs on an unsecured public network, may unknowingly be hosting an unsecured (http) web site for any remote user/system to access on the same network. The issue has has been mitigated in dbt-core v1.6.15, dbt-core v1.7.15, and dbt-core v1.8.1 by binding to localhost explicitly by default in `dbt docs serve`.

Weakness: CWE-1327 (Binding to an Unrestricted IP Address)

## Which versions are affected by CVE-2024-36105?

7 open source packages ship an affected version, including dbt-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbt-core` | PyPI | All versions | 1.6.15, 1.7.15, 1.8.1 |
| `dbt-core` | PyPI | All versions | 1.6.15 |
| `dbt-core` | PyPI | All versions | 1.6.15 |
| `dbt-core` | PyPI | From 1.7.0 | 1.7.15 |
| `dbt-core` | PyPI | From 1.7.0 | 1.7.15 |
| `dbt-core` | PyPI | From 1.8.0 | 1.8.1 |
| `dbt-core` | PyPI | From 1.8.0 | 1.8.1 |

## How do I fix CVE-2024-36105?

Upgrade dbt-core to a fixed version for your release line: 1.6.15, 1.7.15 or 1.8.1.

## Is CVE-2024-36105 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36105 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36105 and fix it if it is affected.

What it is: CVE-2024-36105 is a medium-severity vulnerability in dbt-labs dbt-core, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36105 exists.

Affected packages and fixed versions:
- dbt-core (PyPI): affected all versions; fixed in 1.6.15, 1.7.15, 1.8.1
- dbt-core (PyPI): affected all versions; fixed in 1.6.15
- dbt-core (PyPI): affected all versions; fixed in 1.6.15
- dbt-core (PyPI): affected from 1.7.0; fixed in 1.7.15
- dbt-core (PyPI): affected from 1.7.0; fixed in 1.7.15
- dbt-core (PyPI): affected from 1.8.0; fixed in 1.8.1
- dbt-core (PyPI): affected from 1.8.0; fixed in 1.8.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-36105/ (Markdown: https://insights.sbomify.com/CVE-2024-36105/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36105
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36105
- OSV: https://osv.dev/vulnerability/CVE-2024-36105

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-36105/
Summaries are generated and may contain mistakes; the official description above is the record.