CVE-2024-36105

CVE-2024-36105 is a medium-severity security vulnerability in dbt-core (pip), affecting versions < 1.6.15. It is fixed in 1.6.15, 1.7.15, 1.8.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

dbt allows Binding to an Unrestricted IP Address via socketsocket

Binding to INADDR_ANY (0.0.0.0) or IN6ADDR_ANY (::) exposes an application on all network interfaces, increasing the risk of unauthorized access.

While doing some static analysis and code inspection, I found the following code binding a socket to INADDR_ANY by passing "" as the address. This effectively binds to any network interface on the local system, not just localhost (127.0.0.1).

Details

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 "::".

https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/task/docs/serve.py#L23C38-L23C39

The text around this code also imply the intention is to host docs only on localhost.

PoC

To recreate, run the docs ServeTask.run() to stand up the HTTP server. Then run netstat to see what addresses this process is bound.

Impact

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.

Further references:
https://docs.python.org/3/library/socket.html#socket-families
https://docs.securesauce.dev/rules/PY030
https://cwe.mitre.org/data/definitions/1327.html

CVE-2024-36105 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.15, 1.7.15, 1.8.1); upgrading removes the vulnerable code path.

Affected versions

dbt-core (< 1.6.15) dbt-core (>= 1.7.0, < 1.7.15) dbt-core (= 1.8.0)

Security releases

dbt-core → 1.6.15 (pip) dbt-core → 1.7.15 (pip) dbt-core → 1.8.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

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 (https://github.com/dbt-labs/dbt-core/issues/10209).

Frequently Asked Questions

  1. What is CVE-2024-36105? CVE-2024-36105 is a medium-severity security vulnerability in dbt-core (pip), affecting versions < 1.6.15. It is fixed in 1.6.15, 1.7.15, 1.8.1.
  2. How severe is CVE-2024-36105? CVE-2024-36105 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of dbt-core are affected by CVE-2024-36105? dbt-core (pip) versions < 1.6.15 is affected.
  4. Is there a fix for CVE-2024-36105? Yes. CVE-2024-36105 is fixed in 1.6.15, 1.7.15, 1.8.1. Upgrade to this version or later.
  5. Is CVE-2024-36105 exploitable, and should I be worried? Whether CVE-2024-36105 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2024-36105 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2024-36105?
    • Upgrade dbt-core to 1.6.15 or later
    • Upgrade dbt-core to 1.7.15 or later
    • Upgrade dbt-core to 1.8.1 or later

Other vulnerabilities in dbt-core

Stop the waste.
Protect your environment with Kodem.