<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 08:36:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36105 — dbt allows Binding to an Unrestricted IP Address via socketsocket</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-36105</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dbt-labs dbt-core&lt;/p&gt;
&lt;p&gt;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: `&amp;#39;&amp;#39;` represents `INADDR_ANY`, equivalent to `&amp;#34;0.0.0.0&amp;#34;`. On systems with IPv6, &amp;#39;&amp;#39; represents `IN6ADDR_ANY`, which is equivalent to `&amp;#34;::&amp;#34;`. 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`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dbt-labs dbt-core&lt;/p&gt;
&lt;p&gt;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: `&amp;#39;&amp;#39;` represents `INADDR_ANY`, equivalent to `&amp;#34;0.0.0.0&amp;#34;`. On systems with IPv6, &amp;#39;&amp;#39; represents `IN6ADDR_ANY`, which is equivalent to `&amp;#34;::&amp;#34;`. 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`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-36105</guid>
    </item>
  </channel>
</rss>
