<?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://vulnerability.circl.lu</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 18:03:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-29018 — External DNS requests from 'internal' networks could lead to data exfiltration</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-29018</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; moby, mobyproject moby&lt;/p&gt;
&lt;p&gt;Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby&amp;#39;s networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well.&lt;/p&gt;
&lt;p&gt;When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.&lt;/p&gt;
&lt;p&gt;Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly.&lt;/p&gt;
&lt;p&gt;In addition to configuring the Linux kernel&amp;#39;s various networking features to enable container networking, `dockerd` directly provides some services to container…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; moby, mobyproject moby&lt;/p&gt;
&lt;p&gt;Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby&amp;#39;s networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well.&lt;/p&gt;
&lt;p&gt;When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.&lt;/p&gt;
&lt;p&gt;Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly.&lt;/p&gt;
&lt;p&gt;In addition to configuring the Linux kernel&amp;#39;s various networking features to enable container networking, `dockerd` directly provides some services to container…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-29018</guid>
    </item>
    <item>
      <title>USN-7161-1 — Docker vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-7161-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: docker.io, Ubuntu:Pro:24.04:LTS: docker.io-app&lt;/p&gt;
&lt;p&gt;Yair Zak discovered that Docker could unexpectedly forward DNS requests
from internal networks in an unexpected manner. An attacker could possibly
use this issue to exfiltrate data by encoding information in DNS queries 
to controlled nameservers. This issue was only addressed for the source package
docker.io-app in Ubuntu 24.04 LTS. (CVE-2024-29018)&lt;/p&gt;
&lt;p&gt;Cory Snider discovered that Docker did not properly handle authorization 
plugin request processing. An attacker could possibly use this issue to 
bypass authorization controls by forwarding API requests without their 
full body, leading to unauthorized actions. This issue was only addressed for 
the source package docker.io-app in Ubuntu 24.10 and Ubuntu 24.04 LTS, 
and the source package docker.io in Ubuntu 18.04 LTS. (CVE-2024-41110)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: docker.io, Ubuntu:Pro:24.04:LTS: docker.io-app&lt;/p&gt;
&lt;p&gt;Yair Zak discovered that Docker could unexpectedly forward DNS requests
from internal networks in an unexpected manner. An attacker could possibly
use this issue to exfiltrate data by encoding information in DNS queries 
to controlled nameservers. This issue was only addressed for the source package
docker.io-app in Ubuntu 24.04 LTS. (CVE-2024-29018)&lt;/p&gt;
&lt;p&gt;Cory Snider discovered that Docker did not properly handle authorization 
plugin request processing. An attacker could possibly use this issue to 
bypass authorization controls by forwarding API requests without their 
full body, leading to unauthorized actions. This issue was only addressed for 
the source package docker.io-app in Ubuntu 24.10 and Ubuntu 24.04 LTS, 
and the source package docker.io in Ubuntu 18.04 LTS. (CVE-2024-41110)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-7161-1</guid>
    </item>
  </channel>
</rss>
