Upstream information
Description
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'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.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.
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.
In addition to configuring the Linux kernel's various networking features to enable container networking, `dockerd` directly provides some services to container networks. Principal among these is serving as a resolver, enabling service discovery, and resolution of names from an upstream resolver.
When a DNS request for a name that does not correspond to a container is received, the request is forwarded to the configured upstream resolver. This request is made from the container's network namespace: the level of access and routing of traffic is the same as if the request was made by the container itself.
As a consequence of this design, containers solely attached to an internal network will be unable to resolve names using the upstream resolver, as the container itself is unable to communicate with that nameserver. Only the names of containers also attached to the internal network are able to be resolved.
Many systems run a local forwarding DNS resolver. As the host and any containers have separate loopback devices, a consequence of the design described above is that containers are unable to resolve names from the host's configured resolver, as they cannot reach these addresses on the host loopback device. To bridge this gap, and to allow containers to properly resolve names even when a local forwarding resolver is used on a loopback address, `dockerd` detects this scenario and instead forward DNS requests from the host namework namespace. The loopback resolver then forwards the requests to its configured upstream resolvers, as expected.
Because `dockerd` forwards DNS requests to the host loopback device, bypassing the container network namespace's normal routing semantics entirely, internal networks can unexpectedly forward DNS requests to an external nameserver. By registering a domain for which they control the authoritative nameservers, an attacker could arrange for a compromised container to exfiltrate data by encoding it in DNS queries that will eventually be answered by their nameservers.
Docker Desktop is not affected, as Docker Desktop always runs an internal resolver on a RFC 1918 address.
Moby releases 26.0.0, 25.0.4, and 23.0.11 are patched to prevent forwarding any DNS requests from internal networks. As a workaround, run containers intended to be solely attached to internal networks with a custom upstream address, which will force all upstream DNS queries to be resolved from the container's network namespace.
SUSE information
Overall state of this security issue: Pending
This issue is currently rated as having important severity.
| SUSE | |
|---|---|
| Base Score | 5.9 |
| Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| Attack Vector | Network |
| Attack Complexity | High |
| Privileges Required | None |
| User Interaction | None |
| Scope | Unchanged |
| Confidentiality Impact | High |
| Integrity Impact | None |
| Availability Impact | None |
| CVSSv3 Version | 3.1 |
| SUSE | |
|---|---|
| Base Score | 8.2 |
| Vector | CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| Attack Vector | Network |
| Attack Complexity | High |
| Attack Requirements | None |
| Privileges Required | None |
| User Interaction | None |
| Vulnerable System Confidentiality Impact | High |
| Vulnerable System Integrity Impact | None |
| Vulnerable System Availability Impact | None |
| Subsequent System Confidentiality Impact | None |
| Subsequent System Integrity Impact | None |
| Subsequent System Availability Impact | None |
| CVSSv4 Version | 4.0 |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products under general support and receiving all security fixes. | ||
| SLES15-SP5-CHOST-BYOS-Aliyun | docker | Already fixed |
| SLES15-SP5-CHOST-BYOS-Azure | docker | Already fixed |
| SLES15-SP5-CHOST-BYOS-EC2 | docker | Already fixed |
| SLES15-SP5-CHOST-BYOS-GCE | docker | Already fixed |
| SLES15-SP5-CHOST-BYOS-SAP-CCloud | docker | Already fixed |
| SLES15-SP6-CHOST-BYOS | docker | Already fixed |
| SLES15-SP6-CHOST-BYOS-Aliyun | docker | Already fixed |
| SLES15-SP6-CHOST-BYOS-Azure | docker | Already fixed |
| SLES15-SP6-CHOST-BYOS-EC2 | docker | Already fixed |
| SLES15-SP6-CHOST-BYOS-GCE | docker | Already fixed |
| SLES15-SP6-CHOST-BYOS-GDC | docker | Already fixed |
| SLES15-SP6-CHOST-BYOS-SAP-CCloud | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 12 | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP5 | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP6 | docker | Already fixed |
| SUSE Linux Enterprise Micro 5.1 | docker | Already fixed |
| SUSE Linux Enterprise Micro 5.2 | docker | Already fixed |
| SUSE Linux Enterprise Micro 5.3 | docker | Already fixed |
| SUSE Linux Enterprise Micro 5.4 | docker | Already fixed |
| SUSE Linux Enterprise Micro 5.5 | docker | Already fixed |
| SUSE Linux Enterprise Micro 6.0 | docker | Affected |
| SUSE Linux Enterprise Module for Containers 15 SP5 | docker | Already fixed |
| SUSE Linux Enterprise Module for Containers 15 SP6 | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP5 | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP6 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 15 SP5 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 15 SP6 | docker | Already fixed |
| SUSE Manager Proxy 4.3 | docker | Already fixed |
| SUSE Manager Retail Branch Server 4.3 | docker | Already fixed |
| SUSE Manager Server 4.3 | docker | Already fixed |
| openSUSE Leap 15.5 | docker | Already fixed |
| openSUSE Leap 15.6 | docker | Already fixed |
| openSUSE Leap Micro 5.5 | docker | Already fixed |
| Products under Long Term Service Pack support and receiving important and critical security fixes. | ||
| SLES15-EC2-CHOST-HVM-BYOS | docker | Already fixed |
| SLES15-SP1-CHOST-BYOS-Azure | docker | Already fixed |
| SLES15-SP1-CHOST-BYOS-EC2 | docker | Already fixed |
| SLES15-SP1-CHOST-BYOS-GCE | docker | Already fixed |
| SLES15-SP2-CHOST-BYOS-Aliyun | docker | Already fixed |
| SLES15-SP2-CHOST-BYOS-Azure | docker | Already fixed |
| SLES15-SP2-CHOST-BYOS-EC2 | docker | Already fixed |
| SLES15-SP2-CHOST-BYOS-GCE | docker | Already fixed |
| SLES15-SP3-CHOST-BYOS-Aliyun | docker | Already fixed |
| SLES15-SP3-CHOST-BYOS-Azure | docker | Already fixed |
| SLES15-SP3-CHOST-BYOS-EC2 | docker | Already fixed |
| SLES15-SP3-CHOST-BYOS-GCE | docker | Already fixed |
| SLES15-SP3-CHOST-BYOS-SAP-CCloud | docker | Already fixed |
| SLES15-SP4-CHOST-BYOS | docker | Already fixed |
| SLES15-SP4-CHOST-BYOS-Aliyun | docker | Already fixed |
| SLES15-SP4-CHOST-BYOS-Azure | docker | Already fixed |
| SLES15-SP4-CHOST-BYOS-EC2 | docker | Already fixed |
| SLES15-SP4-CHOST-BYOS-GCE | docker | Already fixed |
| SLES15-SP4-CHOST-BYOS-SAP-CCloud | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP2 | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP2-ESPOS | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP3 | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP3-ESPOS | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP4 | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS | docker | Already fixed |
| SUSE Linux Enterprise Module for Containers 15 SP2 | docker | Already fixed |
| SUSE Linux Enterprise Module for Containers 15 SP3 | docker | Already fixed |
| SUSE Linux Enterprise Module for Containers 15 SP4 | docker | Already fixed |
| SUSE Linux Enterprise Server 12 SP5 | docker | Already fixed |
| SUSE Linux Enterprise Server 12 SP5-LTSS | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP2 | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP2-LTSS | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP3 | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP3-LTSS | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP4 | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP4-LTSS | docker | Already fixed |
| SUSE Linux Enterprise Server LTSS Extended Security 12 SP5 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 12 SP5 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 15 SP2 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 15 SP3 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 15 SP4 | docker | Already fixed |
| Products past their end of life and not receiving proactive updates anymore. | ||
| SUSE CaaS Platform 3.0 | docker | Already fixed |
| SUSE CaaS Platform 4.0 | docker | Already fixed |
| SUSE Enterprise Storage 6 | docker | Already fixed |
| SUSE Enterprise Storage 7 | docker | Already fixed |
| SUSE Enterprise Storage 7.1 | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP1 | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP1-ESPOS | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15-ESPOS | docker | Already fixed |
| SUSE Linux Enterprise High Performance Computing 15-LTSS | docker | Already fixed |
| SUSE Linux Enterprise Micro 5.0 | docker | Already fixed |
| SUSE Linux Enterprise Module for Containers 12 | docker | Already fixed |
| SUSE Linux Enterprise Module for Containers 15 | docker | Already fixed |
| SUSE Linux Enterprise Module for Containers 15 SP1 | docker | Already fixed |
| SUSE Linux Enterprise Server 12 | docker | Already fixed |
| SUSE Linux Enterprise Server 12 SP3 | docker | Already fixed |
| SUSE Linux Enterprise Server 12 SP4 | docker | Already fixed |
| SUSE Linux Enterprise Server 15 | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP1 | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP1-BCL | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP1-LTSS | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP2-BCL | docker | Already fixed |
| SUSE Linux Enterprise Server 15 SP3-BCL | docker | Already fixed |
| SUSE Linux Enterprise Server 15-LTSS | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 12 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 12 SP3 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 12 SP4 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 15 | docker | Already fixed |
| SUSE Linux Enterprise Server for SAP Applications 15 SP1 | docker | Already fixed |
| SUSE Manager Proxy 4.0 | docker | Already fixed |
| SUSE Manager Proxy 4.1 | docker | Already fixed |
| SUSE Manager Proxy 4.2 | docker | Already fixed |
| SUSE Manager Retail Branch Server 4.0 | docker | Already fixed |
| SUSE Manager Retail Branch Server 4.1 | docker | Already fixed |
| SUSE Manager Retail Branch Server 4.2 | docker | Already fixed |
| SUSE Manager Server 4.0 | docker | Already fixed |
| SUSE Manager Server 4.1 | docker | Already fixed |
| SUSE Manager Server 4.2 | docker | Already fixed |
| SUSE OpenStack Cloud 6 | docker | Already fixed |
| SUSE OpenStack Cloud 6-LTSS | docker | Already fixed |
| openSUSE Leap 15.3 | docker | Already fixed |
| openSUSE Leap 15.4 | docker | Already fixed |
| openSUSE Leap Micro 5.2 | docker | Already fixed |
| openSUSE Leap Micro 5.3 | docker | Already fixed |
| openSUSE Leap Micro 5.4 | docker | Already fixed |
| Products at an unknown state of their lifecycle. | ||
| SLES15-SP5-CHOST-BYOS-GDC | docker | Already fixed |
SUSE Timeline for this CVE
CVE page created: Wed Mar 20 23:00:23 2024CVE page last modified: Tue Dec 3 16:06:37 2024